CVE-2026-43107

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-05-06. 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:

xfrm: account XFRMA_IF_ID in aevent size calculation

xfrm_get_ae() allocates the reply skb with xfrm_aevent_msgsize(), then build_aevent() appends attributes including XFRMA_IF_ID when x->if_id is set.

xfrm_aevent_msgsize() does not include space for XFRMA_IF_ID. For states with if_id, build_aevent() can fail with -EMSGSIZE and hit BUG_ON(err < 0) in xfrm_get_ae(), turning a malformed netlink interaction into a kernel panic.

Account XFRMA_IF_ID in the size calculation unconditionally and replace the BUG_ON with normal error unwinding.

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

May 6, 2026

Last Modified

May 11, 2026

Advisory Details (4)

Auto-updated Aug 2, 2026
No patch confirmed yet.
generic

xfrm: account XFRMA_IF_ID in aevent size calculation - kernel/git/stable/linux.git - Linux kernel stable tree

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

xfrm: account XFRMA_IF_ID in aevent size calculation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7081d46d32312f1a31f0e0e99c6835a394037599
generic

xfrm: account XFRMA_IF_ID in aevent size calculation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/58e5735d1a5373652f405a0c16e54ac04aaab0ad
generic

xfrm: account XFRMA_IF_ID in aevent size calculation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2c41283d94af943a05f7f2cc1a01f0c872f3cf43

Vendor Advisories for CVE-2026-43107(1)

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

Patch Availability(15)

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc5-1~exp1 (335 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (126 versions)6.19.14-1

Weakness Classification(1)

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

All Vendor Advisories

(14)

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-43107?
CVE-2026-43107 is a medium vulnerability published on May 6, 2026. In the Linux kernel, the following vulnerability has been resolved: xfrm: account XFRMAIFID in aevent size calculation xfrmgetae() allocates the reply skb with xfrmaeventmsgsize(), then buildaevent() appends attributes including XFRMAIFID when x->ifid is set. xfrmaeventmsgsize() does not include…
When was CVE-2026-43107 disclosed?
CVE-2026-43107 was first published in the National Vulnerability Database on May 6, 2026, with the most recent update on May 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43107 actively exploited?
CVE-2026-43107 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-43107?
CVE-2026-43107 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-43107?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43107, 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-43107

Explore →

Is Your Infrastructure Affected by CVE-2026-43107?

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