CVE-2022-4696

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2023-01-11. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

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

There exists a use-after-free vulnerability in the Linux kernel through io_uring and the IORING_OP_SPLICE operation. If IORING_OP_SPLICE is missing the IO_WQ_WORK_FILES flag, which signals that the operation won't use current->nsproxy, so its reference counter is not increased. This assumption is not always true as calling io_splice on specific files will call the get_uts function which will use current->nsproxy leading to invalidly decreasing its reference counter later causing the use-after-free vulnerability. We recommend upgrading to version 5.10.160 or above

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/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
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
36%
KEV
Not listed

Published

January 11, 2023

Last Modified

September 1, 2026

Advisory Details (3)

Auto-updated Sep 1, 2026
No patch confirmed yet.
generic

NetApp Product Security

https://security.netapp.com/advisory/ntap-20230223-0003/
generic

🐧🕺

https://kernel.dance/#75454b4bbfc7e6a4dd8338556f36ea9107ddf61a
generic

io_uring: add missing item types for splice request - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.10.y&id=75454b4bbfc7e6a4dd8338556f36ea9107ddf61a

Vendor Advisories for CVE-2022-4696(1)

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

Affected Packages

(5 across 5 ecosystems)
Debian:10(1)
PackageVulnerable rangeFixed inDependents
linux-5.105.10.136-1~deb10u1, 5.10.136-1~deb10u2, 5.10.136-1~deb10u3, 5.10.149-2~deb10u1, 5.10.158-2~deb10u15.10.162-1~deb10u1—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (24 versions)5.10.162-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux—5.14.6-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—5.14.6-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—5.14.6-1—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 7× in last 7d / 29× 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 152 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2022-4696?
CVE-2022-4696 is a high vulnerability published on January 11, 2023. There exists a use-after-free vulnerability in the Linux kernel through iouring and the IORINGOPSPLICE operation. If IORINGOPSPLICE is missing the IOWQWORKFILES flag, which signals that the operation won't use current->nsproxy, so its reference counter is not increased. This assumption is not…
When was CVE-2022-4696 disclosed?
CVE-2022-4696 was first published in the National Vulnerability Database on January 11, 2023, with the most recent update on September 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-4696 actively exploited?
CVE-2022-4696 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 63.7% of all scored CVEs.
What is the CVSS score of CVE-2022-4696?
CVE-2022-4696 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2022-4696?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-4696, 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-2022-4696

Explore →

Is Your Infrastructure Affected by CVE-2022-4696?

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

Start Free Scan →Browse All CVEs