CVE-2025-71239: audit: add fchmodat2() to change attributes class
In the Linux kernel, the following vulnerability has been resolved:
audit: add fchmodat2() to change attributes class
fchmodat2(), introduced in version 6.6 is currently not in the change
attribute class of audit. Calling fchmodat2() to change a file
attribute in the same fashion than chmod() or fchmodat() will bypass
audit rules such as:
-w /tmp/test -p rwa -k test_rwa
The current patch adds fchmodat2() to the change attributes class.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel audit logging gap. A file-permission change path introduced with fchmodat2() was not classified like chmod() and fchmodat(), so some attribute changes could avoid expected audit records. The issue is mainly about monitoring, compliance evidence, and forensic visibility, not a documented privilege-escalation flaw.
Executive priority
Treat this as a visibility and assurance issue. It should be prioritized for audited or high-trust Linux systems, but the provided sources do not support emergency handling as an actively exploited remote compromise path.
Technical view
Linux kernel audit omitted fchmodat2(), introduced in 6.6, from the change-attributes audit class. Audit watches such as write/read/attribute rules could miss permission or attribute changes made through that syscall. Upstream stable commits add fchmodat2() to the appropriate audit class.
Likely exposure
Systems running affected Linux kernels with auditd or kernel audit rules that rely on attribute-change logging are most relevant. Exposure is higher for regulated servers, shared Linux hosts, and environments where file permission changes are security-significant.
Exploitation context
The source bundle does not show KEV listing or active exploitation. The practical risk is stealthier local activity against audit coverage if an actor already has a way to call the affected syscall on an unpatched kernel.
Researcher notes
Evidence is concise: the vulnerability is the missing audit classification for fchmodat2(). There is no CVSS, CWE, or exploit confirmation in the bundle. Use upstream commits and distribution backport status to determine fixed kernels.
Mitigation direction
Apply Linux vendor kernel updates containing the upstream stable audit fix.
Check distribution advisories because package fixed versions may differ through backports.
Prioritize hosts where audit logs support compliance, detection, or investigations.
Use compensating file integrity or EDR monitoring until patched.
Review audit assumptions for attribute-change coverage on Linux 6.6-era and later kernels.
Validation and detection
Inventory Linux kernel versions on systems using auditd or kernel audit rules.
Confirm whether the vendor kernel includes one of the referenced stable fixes.
Identify audit rules that depend on attribute-change events for protected paths.
Validate in nonproduction that fchmodat2() attribute changes generate expected audit events after patching.
Confirm downstream SIEM detections still receive the expected audit records.
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-2025-71239 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.
0CVSS vectors
3Timeline events
0ADP providers
7Source links
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.
Mar 17, 2026, 09:11 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.