CVE-2024-35887: ax25: fix use-after-free bugs caused by ax25_ds_del_timer
In the Linux kernel, the following vulnerability has been resolved:
ax25: fix use-after-free bugs caused by ax25_ds_del_timer
When the ax25 device is detaching, the ax25_dev_device_down()
calls ax25_ds_del_timer() to cleanup the slave_timer. When
the timer handler is running, the ax25_ds_del_timer() that
calls del_timer() in it will return directly. As a result,
the use-after-free bugs could happen, one of the scenarios
is shown below:
(Thread 1) | (Thread 2)
| ax25_ds_timeout()
ax25_dev_device_down() |
ax25_ds_del_timer() |
del_timer() |
ax25_dev_put() //FREE |
| ax25_dev-> //USE
In order to mitigate bugs, when the device is detaching, use
timer_shutdown_sync() to stop the timer.
Security readout for executives and security teams
Plain-English summary
A race condition in Linux AX.25 device shutdown can let a timer access memory after it has been freed. This may cause a crash or potentially compromise confidentiality and integrity. The supplied CVSS score is 8.8, but exposure depends on affected kernel code and AX.25 device activity.
Executive priority
Prioritize remediation for systems using AX.25 or operating in environments where adjacent access is plausible. Treat other systems as verification-driven rather than universally exposed. Because impact is rated high but exploitation is unconfirmed, schedule prompt patching without declaring an active incident solely from this CVE.
Technical view
During AX.25 device detachment, del_timer() could return while ax25_ds_timeout() remained active. ax25_dev_put() could then free the device structure before the handler accessed it, producing a use-after-free. The kernel fix replaces that cleanup behavior with timer_shutdown_sync() to synchronously stop the timer.
Likely exposure
Most concern applies to Linux systems running an affected kernel where AX.25 functionality is present and devices may detach. The bundle lists affected versions including 2.6.12, 6.6.26, 6.8.5, and 6.9, but its version representation is incomplete and should be verified against vendor advisories.
Exploitation context
The supplied CVSS vector indicates adjacent-network reachability, low complexity, no privileges, and no user interaction. However, the bundle provides no evidence of public exploitation or weaponization, and the CVE is not identified as being in CISA KEV. Do not treat active exploitation as established.
Researcher notes
The central condition is a teardown race between ax25_dev_device_down() and ax25_ds_timeout(). The source bundle identifies three stable-kernel commits but does not clearly map each commit to every affected branch. Validate branch-specific backports using kernel or distribution records; avoid relying only on displayed version numbers.
Mitigation direction
Update to a vendor kernel release incorporating the applicable upstream fix commit.
Confirm the selected distribution package addresses CVE-2024-35887 before deployment.
If updating is delayed, obtain vendor guidance because the sources name no operational workaround.
Validation and detection
Inventory kernel versions on systems that use or expose AX.25 functionality.
Compare kernel package provenance against vendor advisories and the listed upstream fix commits.
Confirm the deployed kernel contains the applicable timer_shutdown_sync() change.
Review kernel logs for crashes or memory-safety reports involving AX.25 device teardown.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-35887 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
2ADP providers
4Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.