block, bfq: fix uaf for bfqq in bfq_exit_icq_bfqq
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
- 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.
- Fixed version: Linux Linux 1425f1bb5df5239021fd09ebc2a5e8070e705d36, 1ed959fef5b1c6f1a7a3fbea543698c30ebd6678, 246cf66e300b76099b5dbd3fdd39e9a5dbc53f02.
Low priority for now. Upgrade to Linux Linux 1425f1bb5df5239021fd09ebc2a5e8070e705d36, 1ed959fef5b1c6f1a7a3fbea543698c30ebd6678, 246cf66e300b76099b5dbd3fdd39e9a5dbc53f02 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: block, bfq: fix uaf for bfqq in bfq_exit_icq_bfqq Commit 64dc8c732f5c ("block, bfq: fix possible uaf for 'bfqq->bic'") will access 'bic->bfqq' in bic_set_bfqq(), however, bfq_exit_icq_bfqq() can free bfqq first, and then call bic_set_bfqq(), which will cause uaf. Fix the problem by moving bfq_exit_bfqq() behind bic_set_bfqq().
- Published
- Sep 15, 2025
- Updated
- Oct 15, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- CWE-416
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%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.8
- CNA · Linux
- 7.8
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| 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 kernel5.15.86
- linux linux kernel6.0.16
- linux linux kernel6.1.2
- linux linux kernel6.2
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
- 5533742c7cb1bc9b1f0bf401cc397d44a3a9e07a and later · before 1425f1bb5df5239021fd09ebc2a5e8070e705d36affected · git
- 094f3d9314d67691cb21ba091c1b528f6e3c4893 and later · before 7949b0df3dd9f4817ed4a4e989fa9ee81df6205faffected · git
- b22fd72bfebda3956efc4431b60ddfc0a51e03e0 and later · before cfe5b38c37720313eff0dec5517442c7ab3c9a20affected · git
- 761564d93c8265f65543acf0a576b32d66bfa26a and later · before 1ed959fef5b1c6f1a7a3fbea543698c30ebd6678affected · git
- 64dc8c732f5c2b406cc752e6aaa1bd5471159cab and later · before 246cf66e300b76099b5dbd3fdd39e9a5dbc53f02affected · git
- 5.15.86 and later · before 5.15.87affected · semver
- 6.0.16 and later · before 6.0.17affected · semver
- 6.1.2 and later · before 6.1.3affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.4-1 | 6.1.4-1 |
| SUSE:Linux Enterprise Micro 5.2 | kernel-default | before 5.3.18-150300.59.235.1 | 5.3.18-150300.59.235.1 |
| SUSE:Linux Enterprise Micro 5.2 | kernel-default-base | before 5.3.18-150300.59.235.1.150300.18.140.1 | 5.3.18-150300.59.235.1.150300.18.140.1 |
| SUSE:Linux Enterprise Micro 5.2 | kernel-rt | before 5.3.18-150300.235.1 | 5.3.18-150300.235.1 |
| SUSE:Linux Enterprise Micro 5.2 | kernel-source-rt | before 5.3.18-150300.235.1 | 5.3.18-150300.235.1 |
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
Published before and after this one in the same product
- ← EarlierCVE-2022-50315Sep 15, 2025 · ata: ahci: Match EM_MAX_SLOTS with SATA_PMP_MAX_PORTS31Monitor
- ← EarlierCVE-2022-50328Sep 15, 2025 · jbd2: fix potential use-after-free in jbd2_fc_wait_bufs31Monitor
- Later →CVE-2023-53205Sep 15, 2025 · KVM: s390/diag: fix racy access of physical cpu number in diag 9c handler31Monitor
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 | 1425f1bb5df5239021fd09ebc2a5e8070e705d36 | Vendor (CNA) |
| Linux Linux | 1ed959fef5b1c6f1a7a3fbea543698c30ebd6678 | Vendor (CNA) |
| Linux Linux | 246cf66e300b76099b5dbd3fdd39e9a5dbc53f02 | Vendor (CNA) |
| Linux Linux | 5.15.87 | Vendor (CNA) |
| Linux Linux | 6.0.17 | Vendor (CNA) |
| Linux Linux | 6.1.3 | Vendor (CNA) |
| Linux Linux | 7949b0df3dd9f4817ed4a4e989fa9ee81df6205f | Vendor (CNA) |
| Linux Linux | cfe5b38c37720313eff0dec5517442c7ab3c9a20 | Vendor (CNA) |
| debian:linux | 6.1.4-1 · Debian:12 | Package registry (OSV) |
| suse:kernel-default | 5.3.18-150300.59.235.1 · SUSE:Linux Enterprise Micro 5.2 | Package registry (OSV) |
| suse:kernel-default-base | 5.3.18-150300.59.235.1.150300.18.140.1 · SUSE:Linux Enterprise Micro 5.2 | Package registry (OSV) |
| suse:kernel-rt | 5.3.18-150300.235.1 · SUSE:Linux Enterprise Micro 5.2 | Package registry (OSV) |
| suse:kernel-source-rt | 5.3.18-150300.235.1 · SUSE:Linux Enterprise Micro 5.2 | Package registry (OSV) |
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-primary
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.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.