CVE-2025-40363
Description
In the Linux kernel, the following vulnerability has been resolved:
net: ipv6: fix field-spanning memcpy warning in AH output
Fix field-spanning memcpy warnings in ah6_output() and ah6_output_done() where extension headers are copied to/from IPv6 address fields, triggering fortify-string warnings about writes beyond the 16-byte address fields.
memcpy: detected field-spanning write (size 40) of single field "&top_iph->saddr" at net/ipv6/ah6.c:439 (size 16) WARNING: CPU: 0 PID: 8838 at net/ipv6/ah6.c:439 ah6_output+0xe7e/0x14e0 net/ipv6/ah6.c:439
The warnings are false positives as the extension headers are intentionally placed after the IPv6 header in memory. Fix by properly copying addresses and extension headers separately, and introduce helper functions to avoid code duplication.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
A false-positive memcpy warning in the Linux kernel's AH IPv6 output has been fixed by refactoring extension header copying, eliminating a potential kernel panic.
Vulnerability
In the Linux kernel's IPsec subsystem, the *ah6_output() and *ah6_output_done() functions triggered a memcpy: detected field-spanning write warning when copying IPv6 extension headers. The memcpy attempted to write up to 40 bytes into the top_iph->saddr field, which is only 16 bytes wide (the size of an IPv6 address). However, the extension headers are deliberately placed immediately after the IPv6 header in memory, so this write is actually safe. The warning is a false positive from the fortified string APIs [1].
Attack
Vector
No special privileges or network conditions are required to trigger the warning. The alert occurs during normal processing of IPv6 packets with extension headers that pass through the Authentication Header (AH) output path. No authentication or specific network position is needed; any user or process that sends AH-encapsulated IPv6 traffic can trigger this kernel warning [1].
Impact
Because this is a kernel warning (WARN_ON) rather than an error, the immediate impact is limited to a log message and a stack trace. However, depending on the kernel's configuration, repeated warnings could degrade performance or, in systems with panic-on-warn enabled, cause a full system crash. No memory corruption or privilege escalation has been reported [1].
Mitigation
The Linux kernel community fixed the issue by separating the copy of the IPv6 addresses and extension headers into two distinct operations, and by introducing helper functions to avoid code duplication. This eliminates the false warning while preserving functional correctness. The fix is included in the stable kernel trees referenced in [1], [2], and [3]. Systems that have panic-on-warn set should be updated as soon as possible to prevent potential denial-of-service.
AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
2Patches
82da805a61ef59bf27de51bd60bf756ae1e6975b16b2755e1f28dde240160c14cf4109413b056f971bd722327a3d6f65cVulnerability mechanics
Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.
References
8- git.kernel.org/stable/c/0bf756ae1e69fec5e6332c37830488315d6d771bnvd
- git.kernel.org/stable/c/2327a3d6f65ce2fe2634546dde4a25ef52296fecnvd
- git.kernel.org/stable/c/2da805a61ef5272a2773775ce14c3650adb84248nvd
- git.kernel.org/stable/c/75b16b2755e12999ad850756ddfb88ad4bfc7186nvd
- git.kernel.org/stable/c/9bf27de51bd6db5ff827780ec0eba55de230ba45nvd
- git.kernel.org/stable/c/b056f971bd72b373b7ae2025a8f3bd18f69653d3nvd
- git.kernel.org/stable/c/c14cf41094136691c92ef756872570645d61f4a1nvd
- git.kernel.org/stable/c/f28dde240160f3c48a50d641d210ed6a3b9596ednvd
News mentions
0No linked articles in our index yet.