Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-46274: io-wq: check that the predecessor is hashed in io_wq_remove_pending()

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.13% (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 252c5051dba9c709b6a72f2866f93e5e618b3f06, 5.9, 5a20ebf0c81b61f5ea3b1b529c100cad69b9f603; azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 6.6.141.1-1.

Low priority for now. Upgrade to Linux Linux 252c5051dba9c709b6a72f2866f93e5e618b3f06, 5.9, 5a20ebf0c81b61f5ea3b1b529c100cad69b9f603; azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 6.6.141.1-1 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: io-wq: check that the predecessor is hashed in io_wq_remove_pending() io_wq_remove_pending() needs to fix up wq->hash_tail[] if the cancelled work was the tail of its hash bucket. When doing this, it checks whether the preceding entry in acct->work_list has the same hash value, but never checks that the predecessor is hashed at all. io_get_work_hash() is simply atomic_read(&work->flags) >> IO_WQ_HASH_SHIFT, and the hash bits are never set for non-hashed work, so it returns 0. Thus, when a hashed bucket-0 work is cancelled while a non-hashed work is its list predecessor, the check spuriously passes and a pointer to the non-hashed io_kiocb is stored in wq->hash_tail[0]. Because non-hashed work is dequeued via the fast path in io_get_next_work(), which never touches hash_tail[], the stale pointer is never cleared. Therefore, after the non-hashed io_kiocb completes and is freed back to req_cachep, wq->hash_tail[0] is a dangling pointer. The io_wq is per-task (tctx->io_wq) and survives ring open/close, so the dangling pointer persists for the lifetime of the task; the next hashed bucket-0 enqueue dereferences it in io_wq_insert_work() and wq_list_add_after() writes through freed memory. Add the missing io_wq_is_hashed() check so a non-hashed predecessor never inherits a hash_tail[] slot.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Jun 8, 2026
Updated
Aug 5, 2026
EPSS
0.1% · 3th percentile

Report tools

JSON

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.

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.

Follow CVE-2026-46274

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

Affected 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.

VendorProduct
linuxlinux 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.8.6 and later · before 5.9
  • linux linux kernel5.9.1 and later · before 6.6.141
  • linux linux kernel6.7 and later · before 6.12.91
  • linux linux kernel6.13 and later · before 6.18.33
  • linux linux kernel6.19 and later · before 7.0.10
  • linux linux kernel5.9
  • linux linux kernel7.1

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

    • 13f35a2c0fd5c6a4fcd8903542b053bcc914fcf5, 5.9affected
    • 204361a77f4018627addd4a06877448f088ddfc0 and later · before d6bda9df0c0a3080804181464d5c0f4d78a4e769affected · git
    • 204361a77f4018627addd4a06877448f088ddfc0 and later · before 5a20ebf0c81b61f5ea3b1b529c100cad69b9f603affected · git
    • 204361a77f4018627addd4a06877448f088ddfc0 and later · before 252c5051dba9c709b6a72f2866f93e5e618b3f06affected · git
    • 204361a77f4018627addd4a06877448f088ddfc0 and later · before d376c131af7c7739a87ff037ed2fdb67c2542c8aaffected · git
    • 204361a77f4018627addd4a06877448f088ddfc0 and later · before d6a2d7b04b5a093021a7a0e2e69e9d5237dfa8ccaffected · git
    • 5.8.6 and later · before 5.9affected · semver
    • before 5.9not affected · semver
    • 6.6.141 and later · up to and including 6.6.*not affected · semver
    • 6.12.91 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.

EcosystemPackageAffected rangeFix
Debian:12linuxfrom 0—
Debian:13linuxbefore 6.12.94-16.12.94-1
Debian:14linuxbefore 7.0.10-17.0.10-1
openSUSE:Tumbleweedkernel-sourcebefore 7.0.12-1.17.0.12-1.1
SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSkernel-64kbbefore 5.14.21-150400.24.228.15.14.21-150400.24.228.1
SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSkernel-docsbefore 5.14.21-150400.24.228.15.14.21-150400.24.228.1
SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSkernel-obs-buildbefore 5.14.21-150400.24.228.15.14.21-150400.24.228.1
SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSkernel-symsbefore 5.14.21-150400.24.228.15.14.21-150400.24.228.1
SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOSkernel-64kbbefore 5.14.21-150500.55.177.15.14.21-150500.55.177.1
SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOSkernel-docsbefore 5.14.21-150500.55.177.15.14.21-150500.55.177.1
SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOSkernel-obs-buildbefore 5.14.21-150500.55.177.15.14.21-150500.55.177.1
SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOSkernel-symsbefore 5.14.21-150500.55.177.15.14.21-150500.55.177.1
SUSE:Linux Enterprise Live Patching 15 SP4kernel-livepatch-SLE15-SP4_Update_42before 22-150400.2.122-150400.2.1
SUSE:Linux Enterprise Live Patching 15 SP4kernel-livepatch-SLE15-SP4_Update_43before 19-150400.2.119-150400.2.1
SUSE:Linux Enterprise Live Patching 15 SP4kernel-livepatch-SLE15-SP4_Update_45before 16-150400.2.116-150400.2.1
SUSE:Linux Enterprise Live Patching 15 SP4kernel-livepatch-SLE15-SP4_Update_46before 12-150400.2.112-150400.2.1
SUSE:Linux Enterprise Live Patching 15 SP4kernel-livepatch-SLE15-SP4_Update_48before 10-150400.2.110-150400.2.1
SUSE:Linux Enterprise Live Patching 15 SP4kernel-livepatch-SLE15-SP4_Update_49before 8-150400.2.18-150400.2.1
SUSE:Linux Enterprise Live Patching 15 SP4kernel-livepatch-SLE15-SP4_Update_50before 8-150400.2.18-150400.2.1
SUSE:Linux Enterprise Live Patching 15 SP4kernel-livepatch-SLE15-SP4_Update_52before 6-150400.2.16-150400.2.1
SUSE:Linux Enterprise Live Patching 15 SP4kernel-livepatch-SLE15-SP4_Update_57before 1-150400.9.3.11-150400.9.3.1
SUSE:Linux Enterprise Live Patching 15 SP5kernel-livepatch-SLE15-SP5_Update_29before 20-150500.2.120-150500.2.1
SUSE:Linux Enterprise Live Patching 15 SP5kernel-livepatch-SLE15-SP5_Update_30before 17-150500.2.117-150500.2.1
SUSE:Linux Enterprise Live Patching 15 SP5kernel-livepatch-SLE15-SP5_Update_32before 12-150500.2.112-150500.2.1

+84

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • 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 KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-46272Jun 3, 2026 · coresight: tmc-etr: Fix race condition between sysfs and perf mode
    18Monitor
  • ← EarlierCVE-2025-71315Jun 8, 2026 · drm/vkms: Convert to DRM's vblank timer
    22Monitor
  • Later →CVE-2026-46276Jun 8, 2026 · drm/amdgpu: fix zero-size GDS range init on RDNA4
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux252c5051dba9c709b6a72f2866f93e5e618b3f06Vendor (CNA)
Linux Linux5.9Vendor (CNA)
Linux Linux5a20ebf0c81b61f5ea3b1b529c100cad69b9f603Vendor (CNA)
Linux Linuxd376c131af7c7739a87ff037ed2fdb67c2542c8aVendor (CNA)
Linux Linuxd6a2d7b04b5a093021a7a0e2e69e9d5237dfa8ccVendor (CNA)
Linux Linuxd6bda9df0c0a3080804181464d5c0f4d78a4e769Vendor (CNA)
azl3 kernel 6.6.139.1-1 on Azure Linux 3.06.6.141.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.12.94-1 · Debian:13Package registry (OSV)
opensuse:kernel-source7.0.12-1.1 · openSUSE:TumbleweedPackage registry (OSV)
suse:kernel-livepatch-SLE16_Update_87-160000.1.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-livepatch-SLE16_Update_96-160000.1.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-livepatch-SLE16-RT_Update_015-160000.3.4 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-livepatch-SLE16-RT_Update_114-160000.1.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-livepatch-SLE16-RT_Update_212-160000.1.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-livepatch-SLE16-RT_Update_311-160000.1.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-livepatch-SLE16-RT_Update_411-160000.1.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-livepatch-SLE16-RT_Update_510-160000.1.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-livepatch-SLE16-RT_Update_69-160000.1.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-livepatch-SLE16-RT_Update_78-160000.1.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-livepatch-SLE16-RT_Update_87-160000.1.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-livepatch-SLE16-RT_Update_96-160000.1.1 · SUSE:Linux Micro 6.2Package 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.

No history yet (it accumulates with the daily EPSS job).

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.

Finders, 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 Free

CVSS 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.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
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

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records