CVE-2026-46315

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-06-09. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

June 9, 2026

Last Modified

July 23, 2026

Advisory Details (4)

Auto-updated Jul 9, 2026
No patch confirmed yet.
generic

io_uring/waitid: clear waitid info before copying it to userspace - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b737c6612c60c23b40a9f31749b99e6f61943847
generic

io_uring/waitid: clear waitid info before copying it to userspace - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/954518e5a4a5efc5033253f6e36fc7b9f98363a3
generic

io_uring/waitid: clear waitid info before copying it to userspace - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/93d93f5f8da791e98159795c6ef683f45bd95d13
generic

io_uring/waitid: clear waitid info before copying it to userspace - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4d2a0de611ab60d02fc768ae0cd5918b16bd5474

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.

Patch Availability(10)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (141 versions)7.0.12-1

All Vendor Advisories

(10)

Data Freshness Timeline

(refreshed 8× in last 7d / 40× 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.

Showing the most recent 100 of 189 total refreshes for this CVE.

  1. 2026-09-14 04:41 UTCEG score recompute
  2. 2026-09-14 04:41 UTCVendor advisory
  3. 2026-09-14 04:41 UTCGHSA enrichment
  4. 2026-09-13 16:47 UTCEPSS rescore
  5. 2026-09-12 15:01 UTCEPSS rescore
  6. 2026-09-11 14:53 UTCEPSS rescore
  7. 2026-09-11 09:37 UTCEPSS rescore
  8. 2026-09-10 09:34 UTCEPSS rescore
  9. 2026-09-08 22:00 UTCEPSS rescore
  10. 2026-09-07 16:01 UTCEPSS rescore
  11. 2026-09-06 13:47 UTCEPSS rescore
  12. 2026-09-04 05:06 UTCEPSS rescore
  13. 2026-09-02 14:12 UTCEPSS rescore
  14. 2026-09-01 13:54 UTCEPSS rescore
  15. 2026-08-31 01:03 UTCEG score recompute
  16. 2026-08-31 01:03 UTCVendor advisory
  17. 2026-08-31 01:03 UTCGHSA enrichment
  18. 2026-08-30 19:17 UTCEPSS rescore
  19. 2026-08-30 01:22 UTCEPSS rescore
  20. 2026-08-28 21:41 UTCEPSS rescore
  21. 2026-08-27 14:25 UTCEPSS rescore
  22. 2026-08-26 14:46 UTCEPSS rescore
  23. 2026-08-25 13:49 UTCEPSS rescore
  24. 2026-08-25 00:55 UTCEG score recompute
  25. 2026-08-25 00:55 UTCVendor advisory
Show 75 more
  1. 2026-08-25 00:54 UTCGHSA enrichment
  2. 2026-08-23 11:18 UTCEG score recompute
  3. 2026-08-23 11:18 UTCVendor advisory
  4. 2026-08-23 11:18 UTCGHSA enrichment
  5. 2026-08-21 23:49 UTCEPSS rescore
  6. 2026-08-21 12:25 UTCEG score recompute
  7. 2026-08-21 12:25 UTCVendor advisory
  8. 2026-08-21 12:25 UTCGHSA enrichment
  9. 2026-08-20 22:55 UTCEPSS rescore
  10. 2026-08-20 09:22 UTCEG score recompute
  11. 2026-08-20 09:22 UTCVendor advisory
  12. 2026-08-20 09:22 UTCGHSA enrichment
  13. 2026-08-19 17:04 UTCEPSS rescore
  14. 2026-08-18 13:48 UTCEPSS rescore
  15. 2026-08-17 13:47 UTCEPSS rescore
  16. 2026-08-17 01:00 UTCEG score recompute
  17. 2026-08-17 01:00 UTCVendor advisory
  18. 2026-08-17 01:00 UTCGHSA enrichment
  19. 2026-08-16 14:56 UTCEPSS rescore
  20. 2026-08-16 02:14 UTCEPSS rescore
  21. 2026-08-15 18:18 UTCEG score recompute
  22. 2026-08-15 18:18 UTCVendor advisory
  23. 2026-08-15 18:18 UTCGHSA enrichment
  24. 2026-08-15 01:30 UTCEPSS rescore
  25. 2026-08-14 15:21 UTCEG score recompute
  26. 2026-08-14 15:21 UTCVendor advisory
  27. 2026-08-14 15:21 UTCGHSA enrichment
  28. 2026-08-13 22:00 UTCEPSS rescore
  29. 2026-08-13 13:30 UTCEG score recompute
  30. 2026-08-13 13:30 UTCVendor advisory
  31. 2026-08-13 13:30 UTCGHSA enrichment
  32. 2026-08-12 13:51 UTCEPSS rescore
  33. 2026-08-12 11:24 UTCEG score recompute
  34. 2026-08-12 11:24 UTCVendor advisory
  35. 2026-08-12 11:24 UTCGHSA enrichment
  36. 2026-08-11 09:33 UTCEG score recompute
  37. 2026-08-11 09:33 UTCVendor advisory
  38. 2026-08-11 09:33 UTCGHSA enrichment
  39. 2026-08-11 00:00 UTCEPSS rescore
  40. 2026-08-10 07:41 UTCEG score recompute
  41. 2026-08-10 07:40 UTCGHSA enrichment
  42. 2026-08-09 13:46 UTCEPSS rescore
  43. 2026-08-09 05:50 UTCEG score recompute
  44. 2026-08-09 05:50 UTCVendor advisory
  45. 2026-08-09 05:50 UTCGHSA enrichment
  46. 2026-08-08 16:37 UTCEPSS rescore
  47. 2026-08-08 04:00 UTCEG score recompute
  48. 2026-08-08 04:00 UTCVendor advisory
  49. 2026-08-08 04:00 UTCGHSA enrichment
  50. 2026-08-07 02:09 UTCEG score recompute
  51. 2026-08-07 02:09 UTCVendor advisory
  52. 2026-08-07 02:09 UTCGHSA enrichment
  53. 2026-08-06 13:47 UTCEPSS rescore
  54. 2026-08-06 00:18 UTCEG score recompute
  55. 2026-08-06 00:18 UTCVendor advisory
  56. 2026-08-06 00:18 UTCGHSA enrichment
  57. 2026-08-05 19:17 UTCEPSS rescore
  58. 2026-08-04 22:28 UTCEG score recompute
  59. 2026-08-04 22:28 UTCVendor advisory
  60. 2026-08-04 22:27 UTCGHSA enrichment
  61. 2026-08-04 15:10 UTCEPSS rescore
  62. 2026-08-04 10:39 UTCEPSS rescore
  63. 2026-08-03 20:37 UTCEG score recompute
  64. 2026-08-03 20:37 UTCVendor advisory
  65. 2026-08-03 20:37 UTCGHSA enrichment
  66. 2026-08-03 10:36 UTCEPSS rescore
  67. 2026-08-02 18:46 UTCVendor advisory
  68. 2026-08-02 18:46 UTCGHSA enrichment
  69. 2026-08-01 16:55 UTCEG score recompute
  70. 2026-08-01 16:55 UTCVendor advisory
  71. 2026-08-01 16:55 UTCGHSA enrichment
  72. 2026-08-01 04:16 UTCEPSS rescore
  73. 2026-07-31 15:04 UTCEG score recompute
  74. 2026-07-31 15:04 UTCGHSA enrichment
  75. 2026-07-30 16:28 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-46315?
CVE-2026-46315 is a medium 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 July 23, 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 0% probability of exploitation in the next 30 days, which ranks it in the top 98.4% of all scored CVEs.
What is the CVSS score of CVE-2026-46315?
CVE-2026-46315 has a CVSS v3 base score of 5.5 (NVD).
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

See which npm, PyPI, Go, and Maven packages are affected by 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.