blk-cgroup: fix UAF in __blkcg_rstat_flush()
In the Linux kernel, the following vulnerability has been resolved: blk-cgroup: fix UAF in __blkcg_rstat_flush() When multiple blkgs in the same blkcg are released concurrently, a use-after-free can occur. The race happens when one blkg's __blkcg_rstat_flush() removes another blkg's iostat entries via llist_del_all(). The second blkg sees an empty list and proceeds to free itself while the first is still iterating over its entries. Move the flush from __blkg_release() (RCU callback) to blkg_release() (before call_rcu). This ensures the RCU grace period waits for any concurrent flush's rcu_read_lock() section to complete before freeing.
- Published
- Jul 19, 2026
- Updated
- Aug 17, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- CWE-416
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.3.9 and later · before 6.4
- linux linux kernel6.4.1 and later · before 6.6.144
- linux linux kernel6.7 and later · before 6.12.95
- linux linux kernel6.13 and later · before 6.18.38
- linux linux kernel6.19 and later · before 7.1.3
- linux linux kernel6.4
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 0f6090d90f627d8c58f939067d6c6821ce1b3c68, 6.4affected
- 20cb1c2fb7568a6054c55defe044311397e01ddb and later · before 96e545410c4f74c89d496c1d5d9ef8d08f14368baffected · git
- 20cb1c2fb7568a6054c55defe044311397e01ddb and later · before bbebd9425cad3573d1527441753899b926525a0faffected · git
- 20cb1c2fb7568a6054c55defe044311397e01ddb and later · before 5e5b7f2ef854936e95dceb6a2fdfefcb7152d2c6affected · git
- 20cb1c2fb7568a6054c55defe044311397e01ddb and later · before afebe44facc48a61761e885bbb7f0380d4a603ecaffected · git
- 20cb1c2fb7568a6054c55defe044311397e01ddb and later · before 0ab5ee5a1badb58cbb2242617cb01a4972b1f2a2affected · git
- 6.3.9 and later · before 6.4affected · semver
- before 6.4not affected · semver
- 6.6.144 and later · up to and including 6.6.*not affected · semver
- 6.12.95 and later · up to and including 6.12.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | bpftool | before 4.18.0-553.163.1.el8_10 | 4.18.0-553.163.1.el8_10 |
| AlmaLinux:8 | kernel | before 4.18.0-553.163.1.el8_10 | 4.18.0-553.163.1.el8_10 |
| AlmaLinux:8 | kernel-abi-stablelists | before 4.18.0-553.163.1.el8_10 | 4.18.0-553.163.1.el8_10 |
| AlmaLinux:8 | kernel-core | before 4.18.0-553.163.1.el8_10 | 4.18.0-553.163.1.el8_10 |
| AlmaLinux:8 | kernel-cross-headers | before 4.18.0-553.163.1.el8_10 | 4.18.0-553.163.1.el8_10 |
| AlmaLinux:8 | kernel-debug | before 4.18.0-553.163.1.el8_10 | 4.18.0-553.163.1.el8_10 |
| AlmaLinux:8 | kernel-debug-core | before 4.18.0-553.163.1.el8_10 | 4.18.0-553.163.1.el8_10 |
| AlmaLinux:8 | kernel-debug-devel | before 4.18.0-553.163.1.el8_10 | 4.18.0-553.163.1.el8_10 |
| AlmaLinux:8 | kernel-debug-modules | before 4.18.0-553.163.1.el8_10 | 4.18.0-553.163.1.el8_10 |
| AlmaLinux:8 | kernel-debug-modules-extra | before 4.18.0-553.163.1.el8_10 | 4.18.0-553.163.1.el8_10 |
| AlmaLinux:8 | kernel-devel | before 4.18.0-553.163.1.el8_10 | 4.18.0-553.163.1.el8_10 |
| AlmaLinux:8 | kernel-doc | before 4.18.0-553.163.1.el8_10 | 4.18.0-553.163.1.el8_10 |
| AlmaLinux:8 | kernel-headers | before 4.18.0-553.163.1.el8_10 | 4.18.0-553.163.1.el8_10 |
| AlmaLinux:8 | kernel-modules | before 4.18.0-553.163.1.el8_10 | 4.18.0-553.163.1.el8_10 |
| AlmaLinux:8 | kernel-modules-extra | before 4.18.0-553.163.1.el8_10 | 4.18.0-553.163.1.el8_10 |
| AlmaLinux:8 | kernel-rt | before 4.18.0-553.163.1.rt7.504.el8_10 | 4.18.0-553.163.1.rt7.504.el8_10 |
| AlmaLinux:8 | kernel-rt-core | before 4.18.0-553.163.1.rt7.504.el8_10 | 4.18.0-553.163.1.rt7.504.el8_10 |
| AlmaLinux:8 | kernel-rt-debug | before 4.18.0-553.163.1.rt7.504.el8_10 | 4.18.0-553.163.1.rt7.504.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-core | before 4.18.0-553.163.1.rt7.504.el8_10 | 4.18.0-553.163.1.rt7.504.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-devel | before 4.18.0-553.163.1.rt7.504.el8_10 | 4.18.0-553.163.1.rt7.504.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-modules | before 4.18.0-553.163.1.rt7.504.el8_10 | 4.18.0-553.163.1.rt7.504.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-modules-extra | before 4.18.0-553.163.1.rt7.504.el8_10 | 4.18.0-553.163.1.rt7.504.el8_10 |
| AlmaLinux:8 | kernel-rt-devel | before 4.18.0-553.163.1.rt7.504.el8_10 | 4.18.0-553.163.1.rt7.504.el8_10 |
| AlmaLinux:8 | kernel-rt-modules | before 4.18.0-553.163.1.rt7.504.el8_10 | 4.18.0-553.163.1.rt7.504.el8_10 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
- CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV83Now
- CVE-2019-13272In the Linux kernel before 5.1.17, ptrace_link in kernel/ptrace.c mishandles the recording of the credentials of a process that wants to creKEV77This week
- CVE-2013-6282The (1) get_user and (2) put_user API functions in the Linux kernel before 3.5.5 on the v6k and v7 ARM platforms do not validate certain addKEV77This week
- CVE-2013-2094The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows loKEV77This week
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0ab5ee5a1badb58cbb2242617cb01a4972b1f2a2 | Vendor (CNA) |
| Linux Linux | 5e5b7f2ef854936e95dceb6a2fdfefcb7152d2c6 | Vendor (CNA) |
| Linux Linux | 6.4 | Vendor (CNA) |
| Linux Linux | 96e545410c4f74c89d496c1d5d9ef8d08f14368b | Vendor (CNA) |
| Linux Linux | afebe44facc48a61761e885bbb7f0380d4a603ec | Vendor (CNA) |
| Linux Linux | bbebd9425cad3573d1527441753899b926525a0f | Vendor (CNA) |
| azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 | 6.6.150.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| almalinux:bpftool | 4.18.0-553.163.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel | 4.18.0-553.163.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-abi-stablelists | 4.18.0-553.163.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-core | 4.18.0-553.163.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-cross-headers | 4.18.0-553.163.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug | 4.18.0-553.163.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-core | 4.18.0-553.163.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-devel | 4.18.0-553.163.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-modules | 4.18.0-553.163.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-modules-extra | 4.18.0-553.163.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-devel | 4.18.0-553.163.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-doc | 4.18.0-553.163.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| debian:linux | 6.12.95-1 · Debian:13 | Package registry (OSV) |
| red hat:bpftool | 0:4.18.0-553.163.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:4.18.0-553.163.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel | 0:4.18.0-553.163.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-abi-stablelists | 0:4.18.0-553.163.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-core | 0:4.18.0-553.163.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debug | 0:4.18.0-553.163.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debug-core | 0:4.18.0-553.163.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:4.18.0-553.163.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:4.18.0-553.163.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debug-modules | 0:4.18.0-553.163.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
+4
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);Fixed
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- git.kernel.org/stable/c/0ab5ee5a1badb58cbb2242617cb01a4972b1f2a2
- git.kernel.org/stable/c/5e5b7f2ef854936e95dceb6a2fdfefcb7152d2c6
- git.kernel.org/stable/c/96e545410c4f74c89d496c1d5d9ef8d08f14368b
- git.kernel.org/stable/c/afebe44facc48a61761e885bbb7f0380d4a603ec
- git.kernel.org/stable/c/bbebd9425cad3573d1527441753899b926525a0f
Vendor advisories and official records. Exploit/PoC links are deliberately left out.