CVE-2026-43494

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-21. a secondary CVSS source baseline 7.8; sources differ by 0.0.

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

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

net/rds: reset op_nents when zerocopy page pin fails

When iov_iter_get_pages2() fails in rds_message_zcopy_from_user(), the pinned pages are released with put_page(), and rm->data.op_mmp_znotifier is cleared. But we fail to properly clear rm->data.op_nents.

Later when rds_message_purge() is called from rds_sendmsg() the cleanup loop iterates over the incorrectly non zero number of op_nents and frees them again.

Fix this by properly resetting op_nents when it should be in rds_message_zcopy_from_user().

CVSS v3
7.8
EG Score
7.8(medium)
EPSS
18.9%
KEV
Not listed

Published

May 21, 2026

Last Modified

July 15, 2026

Advisory Details (9)

Auto-updated Jun 4, 2026
No patch confirmed yet.
generic

oss-security - Re: PinTheft Linux LPE

http://www.openwall.com/lists/oss-security/2026/05/21/2
generic

net/rds: reset op_nents when zerocopy page pin fails - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/rds: reset op_nents when zerocopy page pin fails - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/rds: reset op_nents when zerocopy page pin fails - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/rds: reset op_nents when zerocopy page pin fails - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9115669faedccdda100428e2d26fd0aac8c50799
generic

net/rds: reset op_nents when zerocopy page pin fails - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/640e37f58f991546a87540d067279c2c1fa9fe51
generic

net/rds: reset op_nents when zerocopy page pin fails - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/290e833d1acb1093bc121fcdc97f5e6161157479
generic

net/rds: reset op_nents when zerocopy page pin fails - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0bbbff00a15b1df2cac9014d6cf4b6890f473353
generic

net/rds: reset op_nents when zerocopy page pin fails - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/03014551938a0887fa55f18ce49b70158a9c0113

Vendor Advisories for CVE-2026-43494(2)

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

Patch Availability(16)

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.

Weakness Classification(1)

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

Additional Vendor Advisories

(15)

Data Freshness Timeline

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

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

Publicly available exploits

(2 references)

Working exploit code is in the public domain (2 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCjayhutajulu1/CVE-2026-43494-PinTheft-PoC
    First seen May 25, 2026

    Proof-of-concept for CVE-2026-43494 (PinTheft): Linux LPE via RDS zerocopy refcount bug + io_uring fixed buffers → SUID page-cache overwrite. Authorized research only.

    Open source ↗
  • GitHub PoC0xBlackash/CVE-2026-43494
    First seen May 22, 2026

    CVE-2026-43494

    Open source ↗

Frequently asked(5)

What is CVE-2026-43494?
CVE-2026-43494 is a high vulnerability published on May 21, 2026. In the Linux kernel, the following vulnerability has been resolved: net/rds: reset op_nents when zerocopy page pin fails When iovitergetpages2() fails in rdsmessagezcopyfrom_user(), the pinned pages are released with put_page(), and rm->data.opmmpznotifier is cleared. But we fail to properly clear…
When was CVE-2026-43494 disclosed?
CVE-2026-43494 was first published in the National Vulnerability Database on May 21, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43494 actively exploited?
CVE-2026-43494 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 18.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-43494?
CVE-2026-43494 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-43494?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43494, 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-43494

Explore →

Is Your Infrastructure Affected by CVE-2026-43494?

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