CVE-2023-53477: ipv6: Add lwtunnel encap size of all siblings in nexthop calculation
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 4cc59f386991ec9374cb4bc83dbe1c0b5a95033f, aa75d826c221e8d48607aef33836cf872a159cf1, aba298b35619213ca787d08d472049627d8cd012.
Low priority for now. Upgrade to Linux Linux 4cc59f386991ec9374cb4bc83dbe1c0b5a95033f, aa75d826c221e8d48607aef33836cf872a159cf1, aba298b35619213ca787d08d472049627d8cd012 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: ipv6: Add lwtunnel encap size of all siblings in nexthop calculation In function rt6_nlmsg_size(), the length of nexthop is calculated by multipling the nexthop length of fib6_info and the number of siblings. However if the fib6_info has no lwtunnel but the siblings have lwtunnels, the nexthop length is less than it should be, and it will trigger a warning in inet6_rt_notify() as follows: WARNING: CPU: 0 PID: 6082 at net/ipv6/route.c:6180 inet6_rt_notify+0x120/0x130 ...... Call Trace: <TASK> fib6_add_rt2node+0x685/0xa30 fib6_add+0x96/0x1b0 ip6_route_add+0x50/0xd0 inet6_rtm_newroute+0x97/0xa0 rtnetlink_rcv_msg+0x156/0x3d0 netlink_rcv_skb+0x5a/0x110 netlink_unicast+0x246/0x350 netlink_sendmsg+0x250/0x4c0 sock_sendmsg+0x66/0x70 ___sys_sendmsg+0x7c/0xd0 __sys_sendmsg+0x5d/0xb0 do_syscall_64+0x3f/0x90 entry_SYSCALL_64_after_hwframe+0x72/0xdc This bug can be reproduced by script: ip -6 addr add 2002::2/64 dev ens2 ip -6 route add 100::/64 via 2002::1 dev ens2 metric 100 for i in 10 20 30 40 50 60 70; do ip link add link ens2 name ipv_$i type ipvlan ip -6 addr add 2002::$i/64 dev ipv_$i ifconfig ipv_$i up done for i in 10 20 30 40 50 60; do ip -6 route append 100::/64 encap ip6 dst 2002::$i via 2002::1 dev ipv_$i metric 100 done ip -6 route append 100::/64 via 2002::1 dev ipv_70 metric 100 This patch fixes it by adding nexthop_len of every siblings using rt6_nh_nlmsg_size().
- Published
- Oct 1, 2025
- Updated
- Nov 5, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- —
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel4.11 and later · before 5.4.235
- linux linux kernel5.5 and later · before 5.10.173
- linux linux kernel5.11 and later · before 5.15.100
- linux linux kernel5.16 and later · before 6.1.18
- linux linux kernel6.2 and later · before 6.2.5
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.11affected
- beb1afac518dec5a15dc92ba8f0ca016dcf457b4 and later · before aba298b35619213ca787d08d472049627d8cd012affected · git
- beb1afac518dec5a15dc92ba8f0ca016dcf457b4 and later · before da26369377f0b671c14692e2d65ceb38131053e1affected · git
- beb1afac518dec5a15dc92ba8f0ca016dcf457b4 and later · before dcdddb5f490890d058ea1f194d661219e92fe88daffected · git
- beb1afac518dec5a15dc92ba8f0ca016dcf457b4 and later · before e11e4d524eba2d3c8fdf897d7ce3853f7573bae9affected · git
- beb1afac518dec5a15dc92ba8f0ca016dcf457b4 and later · before aa75d826c221e8d48607aef33836cf872a159cf1affected · git
- beb1afac518dec5a15dc92ba8f0ca016dcf457b4 and later · before 4cc59f386991ec9374cb4bc83dbe1c0b5a95033faffected · git
- before 4.11not affected · semver
- 5.4.235 and later · up to and including 5.4.*not affected · semver
- 5.10.173 and later · up to and including 5.10.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.20-1 | 6.1.20-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2023-53474Oct 1, 2025 · x86/MCE/AMD: Use an u64 for bank_map22Monitor
- ← EarlierCVE-2023-53475Oct 1, 2025 · usb: xhci: tegra: fix sleep in atomic call22Monitor
- Later →CVE-2023-53480Oct 1, 2025 · kobject: Add sanity check for kset->kobj.ktype in kset_register()22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 4cc59f386991ec9374cb4bc83dbe1c0b5a95033f | Vendor (CNA) |
| Linux Linux | aa75d826c221e8d48607aef33836cf872a159cf1 | Vendor (CNA) |
| Linux Linux | aba298b35619213ca787d08d472049627d8cd012 | Vendor (CNA) |
| Linux Linux | da26369377f0b671c14692e2d65ceb38131053e1 | Vendor (CNA) |
| Linux Linux | dcdddb5f490890d058ea1f194d661219e92fe88d | Vendor (CNA) |
| Linux Linux | e11e4d524eba2d3c8fdf897d7ce3853f7573bae9 | Vendor (CNA) |
| debian:linux | 6.1.20-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/aa75d826c221e8d48607aef33836cf872a159cf1
- git.kernel.org/stable/c/aba298b35619213ca787d08d472049627d8cd012
- git.kernel.org/stable/c/da26369377f0b671c14692e2d65ceb38131053e1
- git.kernel.org/stable/c/dcdddb5f490890d058ea1f194d661219e92fe88d
- git.kernel.org/stable/c/e11e4d524eba2d3c8fdf897d7ce3853f7573bae9
Vendor advisories and official records. Exploit/PoC links are deliberately left out.