CVE-2025-38639: netfilter: xt_nfacct: don't assume acct name is null-terminated
In the Linux kernel, the following vulnerability has been resolved:
netfilter: xt_nfacct: don't assume acct name is null-terminated
BUG: KASAN: slab-out-of-bounds in .. lib/vsprintf.c:721
Read of size 1 at addr ffff88801eac95c8 by task syz-executor183/5851
[..]
string+0x231/0x2b0 lib/vsprintf.c:721
vsnprintf+0x739/0xf00 lib/vsprintf.c:2874
[..]
nfacct_mt_checkentry+0xd2/0xe0 net/netfilter/xt_nfacct.c:41
xt_check_match+0x3d1/0xab0 net/netfilter/x_tables.c:523
nfnl_acct_find_get() handles non-null input, but the error
printk relied on its presence.
Security readout for executives and security teams
Plain-English summary
A local user may trigger an out-of-bounds kernel memory read when Linux processes a malformed netfilter accounting name. Based on the supplied CVSS assessment, consequences may include sensitive kernel-memory exposure or a system crash. No active exploitation is established by the supplied sources.
Executive priority
Treat as a high-priority kernel maintenance issue on multi-user, shared-hosting, and container-node systems. Accelerate patching where untrusted local users exist. Internet-facing status alone does not imply direct exposure because the documented attack vector is local.
Technical view
The xt_nfacct match validation path passes a potentially non-null-terminated accounting name into an error-formatting operation. KASAN observed a slab-out-of-bounds read in string formatting through nfacct_mt_checkentry(). Linux stable commits correct the unsafe assumption. The supplied data rates this CVSS 3.1 score 7.1 with local, low-privilege access.
Likely exposure
Prioritize Linux systems running affected or unpatched vendor kernels where local users can reach the xt_nfacct/netfilter accounting configuration path. The bundle identifies affected Linux versions or branch points from 3.3 through 6.17, but it does not provide reliable distribution-specific backport status.
Exploitation context
The supplied record is not in KEV and provides no evidence of exploitation in the wild. Triggering is local, requires low privileges according to the CVSS vector, and needs no user interaction. The evidence demonstrates a KASAN-detected out-of-bounds read; it does not document a practical exploit.
Researcher notes
The observed fault is a one-byte-at-a-time slab over-read in lib/vsprintf string handling, reached from nfacct_mt_checkentry(). The error path assumed an accounting name was null-terminated. Source evidence supports confidentiality and availability impact ratings, but does not establish exploit reliability, privilege escalation, affected configuration prerequisites, or weaponization.
Mitigation direction
Install a vendor kernel package containing the applicable Linux stable fix.
Review Linux distribution advisories for branch-specific fixed package versions.
Restrict unnecessary local account access until affected kernels are updated.
Follow vendor guidance if immediate kernel replacement is operationally impractical.
Validation and detection
Inventory running kernel versions across Linux hosts and container nodes.
Check vendor package changelogs for CVE-2025-38639 or referenced fix commits.
Determine whether xt_nfacct functionality is present and operationally required.
Reboot after updating, then confirm the running kernel matches the fixed package.
Review kernel logs for related KASAN or out-of-bounds reports.
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-38639 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.
1CVSS vectors
3Timeline events
1ADP providers
12Source links
CVSS vector scores
1 official score
We 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.