Skip to main content
VulnerabilityPublished Updated

CVE-2026-46315: Linux kernel · io_uring/waitid: clear waitid info before copying it to userspace

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in b737c6612c60c23b40a9f31749b99e6f61943847 : update Linux kernel when convenient.

Data as of 6 Nov 2026, 16:49 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in b737c6612c60c23b40a9f31749b99e6f61943847, 954518e5a4a5efc5033253f6e36fc7b9f98363a3, 93d93f5f8da791e98159795c6ef683f45bd95d13 +1

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade Linux kernel to b737c6612c60c23b40a9f31749b99e6f61943847, 954518e5a4a5efc5033253f6e36fc7b9f98363a3, 93d93f5f8da791e98159795c6ef683f45bd95d13 or 4d2a0de611ab60d02fc768ae0cd5918b16bd5474.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ f31ecf671ddc498f20219453395794ff2383e06b, < b737c6612c60c23b40a9f31749b99e6f61943847
Fixed in
  • b737c6612c60c23b40a9f31749b99e6f61943847
LinuxLinuxAffected
  • ≥ f31ecf671ddc498f20219453395794ff2383e06b, < 954518e5a4a5efc5033253f6e36fc7b9f98363a3
Fixed in
  • 954518e5a4a5efc5033253f6e36fc7b9f98363a3
LinuxLinuxAffected
  • ≥ f31ecf671ddc498f20219453395794ff2383e06b, < 93d93f5f8da791e98159795c6ef683f45bd95d13
Fixed in
  • 93d93f5f8da791e98159795c6ef683f45bd95d13
LinuxLinuxAffected
  • ≥ f31ecf671ddc498f20219453395794ff2383e06b, < 4d2a0de611ab60d02fc768ae0cd5918b16bd5474
Fixed in
  • 4d2a0de611ab60d02fc768ae0cd5918b16bd5474
LinuxLinuxAffected
  • =6.7
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: io_uring/waitid: clear waitid info before copying it to userspace IORING_OP_WAITID stores its result fields in struct io_waitid::info and later copies them to userspace siginfo. The prep path initializes the request arguments, but it does not initialize info itself. If the wait operation completes without reporting a child event, the common wait code can return without writing wo_info. In that case io_waitid_finish() still copies iw->info to userspace, exposing stale bytes from the reused io_kiocb command storage. Clear the result storage during prep so the io_uring path matches the regular waitid syscall, which uses a zero-initialized struct waitid_info.

References

Community reviews

Loading reviews…