CVE-2026-46315

CVSS 0.0
0.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No confirmed exploitation signals yet
CISA-KEV: Not listedEPSS: 0%CVSS: Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
EG Score
0.0(none)
EPSS
5.2%
KEV
Not listed

Published

June 9, 2026

Last Modified

June 14, 2026

Vendor Advisories for CVE-2026-46315(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 7× in last 7d / 49× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 02:23 UTCEPSS rescore
  3. 2026-07-05 02:30 UTCEPSS rescore
  4. 2026-07-04 06:31 UTCEPSS rescore
  5. 2026-07-03 09:05 UTCGHSA enrichment
  6. 2026-07-01 15:07 UTCEPSS rescore
  7. 2026-06-30 23:22 UTCEPSS rescore
  8. 2026-06-30 06:16 UTCGHSA enrichment
  9. 2026-06-29 14:06 UTCEPSS rescore
  10. 2026-06-29 14:06 UTCEPSS rescore
  11. 2026-06-28 14:07 UTCEPSS rescore
  12. 2026-06-28 04:56 UTCEPSS rescore
  13. 2026-06-28 04:56 UTCEPSS rescore
  14. 2026-06-27 07:10 UTCGHSA enrichment
  15. 2026-06-27 03:08 UTCEPSS rescore
  16. 2026-06-25 13:49 UTCEPSS rescore
  17. 2026-06-24 14:05 UTCEPSS rescore
  18. 2026-06-24 08:04 UTCGHSA enrichment
  19. 2026-06-23 21:33 UTCEPSS rescore
  20. 2026-06-23 21:33 UTCEPSS rescore
  21. 2026-06-22 14:25 UTCEPSS rescore
  22. 2026-06-22 14:25 UTCEPSS rescore
  23. 2026-06-21 14:56 UTCEPSS rescore
  24. 2026-06-21 14:56 UTCEPSS rescore
  25. 2026-06-21 06:28 UTCGHSA enrichment
Show 24 more
  1. 2026-06-21 01:59 UTCEPSS rescore
  2. 2026-06-21 01:59 UTCEPSS rescore
  3. 2026-06-19 19:26 UTCEPSS rescore
  4. 2026-06-19 19:26 UTCEPSS rescore
  5. 2026-06-18 17:52 UTCEPSS rescore
  6. 2026-06-18 17:52 UTCEPSS rescore
  7. 2026-06-18 07:17 UTCGHSA enrichment
  8. 2026-06-17 17:53 UTCEPSS rescore
  9. 2026-06-16 17:52 UTCEPSS rescore
  10. 2026-06-15 17:49 UTCEPSS rescore
  11. 2026-06-15 06:57 UTCGHSA enrichment
  12. 2026-06-14 23:33 UTCMITRE cvelistV5
  13. 2026-06-13 23:00 UTCEPSS rescore
  14. 2026-06-12 23:12 UTCEPSS rescore
  15. 2026-06-12 23:12 UTCEPSS rescore
  16. 2026-06-12 07:51 UTCEG score recompute
  17. 2026-06-12 07:51 UTCGHSA enrichment
  18. 2026-06-11 14:00 UTCEPSS rescore
  19. 2026-06-10 22:18 UTCEPSS rescore
  20. 2026-06-10 13:22 UTCEPSS rescore
  21. 2026-06-10 13:22 UTCEPSS rescore
  22. 2026-06-09 09:35 UTCNVD update
  23. 2026-06-09 08:46 UTCEG score recompute
  24. 2026-06-09 08:45 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-46315?
CVE-2026-46315 is a publicly disclosed vulnerability published on June 9, 2026. In the Linux kernel, the following vulnerability has been resolved: io_uring/waitid: clear waitid info before copying it to userspace IORINGOPWAITID 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…
When was CVE-2026-46315 disclosed?
CVE-2026-46315 was first published in the National Vulnerability Database on June 9, 2026, with the most recent update on June 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46315 actively exploited?
CVE-2026-46315 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 5.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2026-46315?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46315, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-46315

Explore →

Is Your Infrastructure Affected by CVE-2026-46315?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.