Cyber Resilience

CVE-2026-43107

Linux Kernel 4.19 – 6.12.83

Published
06 May 2026
Modified
17 June 2026
Patch / advisory
CVSS Score v3.1 5.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0011 2th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2026-43107 is a medium-severity Incorrect Calculation of Buffer Size (CWE-131) vulnerability in Linux Linux Kernel. Its CVSS base score is 5.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Application or System Exploitation (T1499.004); ranked at the 2th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1499.004 Application or System Exploitation Impact
Adversaries may exploit software vulnerabilities that can cause an application or system to crash and deny availability to users.
Why these techniques?

Local kernel bug in xfrm netlink handling allows crafted messages to trigger BUG_ON panic, directly enabling endpoint DoS via system exploitation.

Confidence: MEDIUM · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2024-42259Same product: Linux Linux Kernel
CVE-2023-5158Same product: Linux Linux Kernel
CVE-2024-46684Same product: Linux Linux Kernel
CVE-2023-6560Same product: Linux Linux Kernel
CVE-2024-26721Same product: Linux Linux Kernel
CVE-2023-6039Same product: Linux Linux Kernel
CVE-2024-43843Same product: Linux Linux Kernel
CVE-2026-43302Same product: Linux Linux Kernel
CVE-2026-53091Same product: Linux Linux Kernel
CVE-2024-46729Same product: Linux Linux Kernel

Affected Assets

linux
linux kernel
7.0 · 4.19 — 6.12.83 · 6.13 — 6.18.24 · 6.19 — 6.19.14

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SA-15 Development Process, Standards, and Tools
  • SA-11 Developer Testing and Evaluation
  • SI-10 Information Input Validation
Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)

Mitigating Controls (NIST 800-53 r5) AI

prevent

Requires use of secure development standards and tools that enforce correct buffer/size calculations, directly preventing the XFRMA_IF_ID omission in xfrm_aevent_msgsize().

prevent

Mandates developer testing and evaluation (including fuzzing of netlink paths) that would detect the size-mismatch leading to -EMSGSIZE and BUG_ON.

prevent

Requires validation of all input data sizes and attributes before skb allocation and attribute appending in xfrm_get_ae().

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent buffer-size miscalculations via coding standards, reviews, and testing, while fixing this single weakness only partially fulfills the broader control.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

degrades

Secure coding standards directly require correct buffer-size calculations.

detects

Security testing can detect buffer-size errors before release.

prevents

Secure development lifecycle mandates size-checking practices that reduce buffer-size miscalculations.

prevents

Application security requirements can specify buffer-size validation rules.

prevents

Secure architecture principles include safe memory-allocation guidelines.

References