Security readout for executives and security teams
Plain-English summary
A Linux tracing filesystem permission bug could leave some tracefs files with older customized permissions after an administrator remounts tracefs expecting a permission reset. That can mislead operators and potentially preserve access that should have been removed. The issue is local, not remote, based on the provided CVSS vector.
Executive priority
Treat as high priority for Linux fleets with shared user access or delegated tracing permissions. It is less urgent for single-purpose systems without local untrusted users, but it should still be included in normal kernel patch cycles because incorrect tracing access can expose sensitive runtime behavior.
Technical view
tracefs generated permissions inherited root inode permissions unless a user-set permission flag was present. During remount with permission options, files without custom flags changed, while previously customized files retained old permissions. The fix tracks tracefs inodes and clears permission flags on remount so all entries follow the remounted root permissions.
Likely exposure
Exposure is most relevant on Linux systems running affected kernel versions where tracefs is mounted and administrators use remount options such as gid or permission changes to control tracing access. Multi-user systems and shared build, CI, lab, or operations hosts have higher practical concern.
Exploitation context
The bundle does not show CISA KEV listing or active exploitation. Exploitation requires local access and depends on tracefs permission state being misconfigured or unexpectedly retained. The CVSS vector is local, low complexity, low privilege, no user interaction, with high confidentiality, integrity, and availability impact.
Researcher notes
Evidence is limited to the CVE record and kernel stable commits in the bundle. Do not infer remote exploitability or public exploitation. Key research focus is permission inheritance and stale customized tracefs inode flags across remounts, mapped to CWE-863 improper authorization.
Mitigation direction
- Update to a Linux kernel containing the referenced stable tracefs fix.
- Review vendor kernel advisories for exact fixed package versions.
- Audit tracefs mount options and group access on affected hosts.
- Manually review customized tracefs file permissions after remounts.
- Prioritize shared systems where non-root users can access tracing facilities.
Validation and detection
- Identify Linux kernel versions and compare against vendor fixed releases.
- Check whether tracefs is mounted on production and shared systems.
- Review /sys/kernel/tracing permissions for unexpected group or mode values.
- Confirm remount permission changes apply consistently after patching.
- Document any operational dependency on custom tracefs permissions.
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-863: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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-36963 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.9CISA-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
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/5f91fc82794d4a6e41cdcd02d00baa377d94ca78CVE reference, Linux
- https://git.kernel.org/stable/c/414fb08628143203d29ccd0264b5a83fb9523c03CVE reference, Linux
- https://git.kernel.org/stable/c/baa23a8d4360d981a49913841a726edede5cdd54CVE 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.
Incorrect Authorization
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.