Security readout for executives and security teams
Plain-English summary
This Linux kernel flaw can leave a filesystem inode lock held after an error in AFS address preference handling. The main business risk is local availability disruption, not data theft or remote compromise. The source bundle does not show active exploitation.
Executive priority
Treat as a normal-priority kernel availability fix unless affected systems provide shell access to untrusted users. It should enter routine patching, with faster handling for multi-user servers or environments where local users are less trusted.
Technical view
In fs/afs/addr_prefs.c, afs_proc_addr_prefs_write can return directly after afs_split_string reports a negative argc, bypassing inode unlock cleanup. The fix stores the error and jumps to common cleanup. This is CWE-667 with CVSS 5.5: local, low-privilege, availability-only impact.
Likely exposure
Exposure is most relevant to Linux systems running affected kernel builds with AFS support. The bundle lists Linux kernel versions including 6.8, 6.12.11, and 6.13, plus stable fix commits. Distribution backports may change practical exposure.
Exploitation context
The evidence is a syzbot-reported kernel warning about a lock held when returning to userspace. The source bundle marks KEV false and provides no cited evidence of public exploitation, weaponized exploit code, or remote attack paths.
Researcher notes
The bundle supports a lock-cleanup bug in the AFS proc write path, fixed by routing the error path through common cleanup. Evidence is incomplete for exploitability beyond local availability impact; do not infer confidentiality or integrity risk from the provided sources.
Mitigation direction
- Update to a vendor kernel containing the referenced stable fixes.
- Confirm distribution advisories because kernel fixes may be backported.
- Prioritize internet-facing shared hosts only if local user access exists.
- Schedule reboot or live patching according to normal kernel update practice.
- If no package is available, monitor vendor guidance before deploying custom kernels.
Validation and detection
- Inventory Linux kernel versions across servers and endpoints.
- Check vendor changelogs for the referenced stable commit IDs.
- Identify systems with AFS support enabled or available.
- Review logs for kernel lock warnings related to AFS.
- Confirm patched systems boot the expected fixed kernel.
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-667: 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-2025-21672 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
- Medium
- CVSS
- 5.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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:N/I:N/A:H1.83.6CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
5.5MediumVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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/22be1d90a6211c88dd093b25d1f3aa974d0d9f9dCVE reference, Linux
- https://git.kernel.org/stable/c/17a4fde81d3a7478d97d15304a6d61094a10c2e3CVE 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.
Improper Locking
Improper Locking represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.