CVE-2023-53705
Description
In the Linux kernel, the following vulnerability has been resolved:
ipv6: Fix out-of-bounds access in ipv6_find_tlv()
optlen is fetched without checking whether there is more than one byte to parse. It can lead to out-of-bounds access.
Found by InfoTeCS on behalf of Linux Verification Center (linuxtesting.org) with SVACE.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
In the Linux kernel, ipv6_find_tlv() lacks a length check, leading to an out-of-bounds read when parsing options.
Description
The Linux kernel's IPv6 stack contains an out-of-bounds access vulnerability in the ipv6_find_tlv() function. The function parses IPv6 destination options headers but fails to verify that at least one byte remains before reading the optlen field. This oversight can cause the code to read beyond the intended buffer boundaries when processing a malformed packet [1][2][3]. The issue was discovered by InfoTeCS on behalf of the Linux Verification Center (linuxtesting.org) using the SVACE static analysis tool.
Exploitation
Exploitation requires the ability to send a crafted IPv6 packet to the target system. Specifically, an attacker can construct a destination options header where the option type and length fields are positioned such that the optlen fetch occurs when fewer than two bytes (one byte for type, one for length) remain in the buffer. No authentication is needed, and the attack can be performed remotely if the host is reachable over IPv6.
Impact
A successful out-of-bounds read could leak sensitive kernel memory or cause a kernel crash (denial of service). In some configurations, an attacker might leverage the read to bypass KASLR or other memory protections, though the primary consequence is system instabilty.
Mitigation
The vulnerability has been patched in the Linux kernel. The fix adds a bounds check before reading optlen, ensuring that the function can only proceed when the remaining buffer space is sufficient. Users should update to a kernel version containing the patch [1][2][3]. No workaround is available.
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
1Patches
859e656d0d4a804bf69e3de43011f47c8b838e5f82688ae109b92e2d0eb6991dd8aab9c9fae68c0f7edbc878ecb0897f4Vulnerability 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/011f47c8b8389154f996f5f69da8efc3a3beefefnvd
- git.kernel.org/stable/c/04bf69e3de435d793a203aacc4b774f8f9f2baebnvd
- git.kernel.org/stable/c/59e656d0d4a84ea0ee9a39c6f69160a3effccc94nvd
- git.kernel.org/stable/c/878ecb0897f4737a4c9401f3523fd49589025671nvd
- git.kernel.org/stable/c/91dd8aab9c9f193210681b86b6b92840ffe74f0cnvd
- git.kernel.org/stable/c/9b92e2d0eb696d7586ba832c8854653b59887da0nvd
- git.kernel.org/stable/c/ae68c0f7edbc9a294094ce03a0aaf45aa489ce40nvd
- git.kernel.org/stable/c/e5f82688ae10f5f386952e65e941bb8868ee54dcnvd
News mentions
0No linked articles in our index yet.