Security readout for executives and security teams
Plain-English summary
A Linux kernel flaw mishandles a network-device reference when an AX.25 device is detached. A local, low-privileged user may be able to trigger unsafe kernel memory behavior, potentially affecting confidentiality, integrity, and availability. Exposure is narrower where AX.25 is unavailable or unused.
Executive priority
Treat as a high-priority kernel update for systems using AX.25 or allowing untrusted local access. For systems without AX.25 exposure, schedule remediation through normal kernel maintenance after confirming configuration and vendor backport status. No supplied evidence supports emergency action for active exploitation.
Technical view
The AX.25 subsystem releases the wrong device tracker during device teardown. The fix changes ax25_kill_by_device() to release the tracker stored in the AX.25 control block rather than ax25_dev, preventing an already-released reference condition. CVSS 3.1 is 7.8: local access, low complexity, low privileges, and no user interaction.
Likely exposure
Linux systems running an affected kernel are candidates, but practical exposure depends on AX.25 support and access to the relevant local networking operations. Distribution backports make version-only conclusions unreliable. The supplied record lists fixes across stable kernel lines but does not provide complete distribution-specific package mappings.
Exploitation context
The supplied evidence characterizes this as a local, low-privilege vulnerability requiring no user interaction. It includes a reproduced refcount warning during AX.25 device teardown. CISA KEV status is false, and the supplied sources provide no evidence of active exploitation or a public exploit.
Researcher notes
The report demonstrates an incorrect reference-tracker release and identifies the corrected ownership location. The supplied CVSS implies potential kernel-level confidentiality, integrity, and availability impact, but the bundle does not document a proven exploitation primitive, affected distribution packages, or observed attacks. Validate backports against vendor source rather than release numbers alone.
Mitigation direction
- Upgrade to a vendor-supported kernel containing the CVE-2024-36009 fix or an equivalent backport.
- Prioritize systems where AX.25 is enabled, configured, or accessible to untrusted local users.
- Consult distribution advisories to identify fixed package versions; upstream versions alone may not reflect backports.
- If immediate patching is impossible, assess disabling unused AX.25 functionality through approved system controls.
Validation and detection
- Inventory kernel versions and distribution package revisions across Linux systems.
- Determine whether AX.25 support is built, loaded, configured, or operationally required.
- Confirm vendor packages include an upstream fix commit or documented equivalent backport.
- Review kernel logs for AX.25 teardown warnings or ref_tracker reports, without treating absence as proof of safety.
- After updating, verify the running kernel matches the installed fixed package.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2024-36009 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9LinuxVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/0d14f104027e30720582448706c7d6b43065c851CVE reference, Linux
- https://git.kernel.org/stable/c/4fee8fa86a15d7790268eea458b1aec69c695530CVE reference, Linux
- https://git.kernel.org/stable/c/c42b073d9af4a5329b25b17390c63ab3847f30e8CVE reference, Linux
- https://git.kernel.org/stable/c/467324bcfe1a31ec65d0cf4aa59421d6b7a7d52bCVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.