Security readout for executives and security teams
Plain-English summary
A flaw in Linux's n_gsm TTY line discipline can cause kernel memory corruption when frame-mode reconfiguration leaves stale length and state values. Successful abuse could compromise confidentiality, integrity, or availability. Severity is high, but exposure depends on local access and n_gsm availability or use; the supplied evidence does not show active exploitation.
Executive priority
Prioritize Linux systems using n_gsm or permitting untrusted local users to configure relevant TTY functionality. Apply supported kernel updates promptly. Systems without this exposure can follow normal kernel patching urgency rather than emergency incident response because active exploitation is not evidenced.
Technical view
Switching from basic to advanced and back to basic framing does not reset gsm->state and gsm->len. Continued input can make gsm0_receive() write beyond gsm->buf. The fix tightens the count-versus-length check and adds MAX_MRU bounds in gsm0_receive() and gsm1_receive(). CVSS 3.1 is 7.8: local, low-complexity, low-privilege, no-interaction exploitation with high potential impact.
Likely exposure
Exposure is limited to Linux systems where the n_gsm TTY line discipline is present and configurable. The CVSS vector requires local access and low privileges. The described trigger also depends on crafted frame input and switching between basic and advanced modes. Confirm exact distribution package status with the relevant vendor.
Exploitation context
The bundle marks KEV false, and no supplied source establishes active exploitation. The required local access and n_gsm-specific conditions reduce broad remote exposure, but successful kernel memory corruption could produce serious system compromise or disruption. Public proof-of-concept availability is not established by the supplied evidence.
Researcher notes
The correction addresses stale parser state across mode reconfiguration and adds independent MAX_MRU safety bounds. The supplied affected-version data is not clear enough for reliable version-only classification, particularly across backported distribution kernels. Validate using vendor package advisories, changelogs, or fix-commit presence. The bundle identifies CWE-125, while its technical description explicitly includes an out-of-bounds write.
Mitigation direction
- Install a vendor-supported kernel update containing the CVE-2024-36016 fix, then reboot into the updated kernel.
- Confirm vendor advisories for each kernel branch; do not infer patch status solely from the displayed version.
- Prioritize systems where n_gsm is deployed or accessible to low-privileged local users.
- If patching is delayed, seek vendor-approved exposure-reduction guidance; the supplied sources name no standalone workaround.
Validation and detection
- Record the running kernel version and distribution package release on every potentially exposed Linux system.
- Determine whether n_gsm is present, deployed, or available to low-privileged local users.
- Verify the installed package includes the relevant upstream fix or an equivalent vendor backport.
- After rebooting, confirm the running kernel matches the patched 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.
CWE-125: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2024-36016 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
2 official scoresWe 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.9LinuxCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H2.55.2CISA-ADPVulnerability 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
Base CVSS 3.1 score
7.7HighVector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/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/9513d4148950b05bc99fa7314dc883cc0e1605e5CVE reference, Linux
- https://git.kernel.org/stable/c/b229bc6c6ea9fe459fc3fa94fd0a27a2f32aca56CVE reference, Linux
- https://git.kernel.org/stable/c/0fb736c9931e02dbc7d9a75044c8e1c039e50f04CVE reference, Linux
- https://git.kernel.org/stable/c/4c267110fc110390704cc065edb9817fdd10ff54CVE reference, Linux
- https://git.kernel.org/stable/c/46f52c89a7e7d2691b97a9728e4591d071ca8abcCVE reference, Linux
- https://git.kernel.org/stable/c/774d83b008eccb1c48c14dc5486e7aa255731350CVE reference, Linux
- https://git.kernel.org/stable/c/f126ce7305fe88f49cdabc6db4168b9318898ea3CVE reference, Linux
- https://git.kernel.org/stable/c/b890d45aaf02b564e6cae2d2a590f9649330857dCVE reference, Linux
- https://git.kernel.org/stable/c/47388e807f85948eefc403a8a5fdc5b406a65d5aCVE reference, Linux
- https://lists.debian.org/debian-lts-announce/2024/06/msg00020.htmlCVE reference, CVE
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.
Out-of-bounds Read
Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.