CVE-2024-40910
ax25: Fix refcount imbalance on inbound connections
Reported by linux · Published July 12, 2024
In the Linux kernel, the following vulnerability has been resolved: ax25: Fix refcount imbalance on inbound connections When releasing a socket in ax25_release(), we call netdev_put() to decrease the refcount on the associated ax.25 device. However, the execution path for accepting an incoming connection never calls netdev_hold(). This imbalance leads to refcount errors, and ultimately to kernel crashes. A typical call trace for the above situation will start with one of the following errors: refcount_t: decrement hit 0; leaking memory. refcount_t: underflow; use-after-free. And will then have a trace like: Call Trace: <TASK> ? show_regs+0x64/0x70 ? __warn+0x83/0x120 ? refcount_warn_saturate+0xb2/0x100 ? report_bug+0x158/0x190 ? prb_read_valid+0x20/0x30 ? handle_bug+0x3e/0x70 ? exc_invalid_op+0x1c/0x70 ? asm_exc_invalid_op+0x1f/0x30 ? refcount_warn_saturate+0xb2/0x100 ? refcount_warn_saturate+0xb2/0x100 ax25_release+0x2ad/0x360 __sock_release+0x35/0xa0 sock_close+0x19/0x20 [...] On reboot (or any attempt to remove the interface), the kernel gets stuck in an infinite loop: unregister_netdevice: waiting for ax0 to become free. Usage count = 0 This patch corrects these issues by ensuring that we call netdev_hold() and ax25_dev_hold() for new connections in ax25_accept(). This makes the logic leading to ax25_accept() match the logic for ax25_bind(): in both cases we increment the refcount, which is ultimately decremented in ax25_release().
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| linux_kernel | linux | 6.9.6, 6.6.35, 6.1.95 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 9fd75b66b8f68498454d685dc4ba13192ae069b0, 9fd75b66b8f68498454d685dc4ba13192ae069b0, 9fd75b66b8f68498454d685dc4ba13192ae069b0 |
| Linux | Linux | 5.18, 0, 6.1.95 |
| linux | linux_kernel | 5.18, 5.18, 5.18 |
| Linux | Linux | 9fd75b66b8f68498454d685dc4ba13192ae069b0, 9fd75b66b8f68498454d685dc4ba13192ae069b0, 9e1e088a57c23251f1cfe9601bbd90ade2ea73b9 |
Timeline
- Jul 12, 2024 CVE Published
- Jul 13, 2024 EPSS Score (30 in total, the first dated here)
- Oct 4, 2024 Coalition ESS Score (11 in total, the first dated here)
- Jan 6, 2025 CVE Updated
- Jan 7, 2026 Security Advisory (326 in total, the first dated here)
- Mar 30, 2026 Distribution Patch (228 in total, the first dated here)
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2024-40910
vulnetix vdb fixes CVE-2024-40910
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2024-40910/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart