CVE-2026-63834: batman-adv: tp_meter: restrict number of unacked list entries
Noroxi assessment
Priority: Monitor (action score 0/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.17% (FIRST EPSS).
- Fixed version: Linux Linux 1111a3381bca2d1f084a07686bc783af5ab23df7, 1c616b0be4bd8399d485e25e91859373b95d6013, 1fb8762600a393d1caccd63be5d07e1756982d68; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 1111a3381bca2d1f084a07686bc783af5ab23df7, 1c616b0be4bd8399d485e25e91859373b95d6013, 1fb8762600a393d1caccd63be5d07e1756982d68; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-1 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: batman-adv: tp_meter: restrict number of unacked list entries When the unacked_list is unbound, an attacker could send messages with small lengths and appropriated seqno + gaps to force the receiver to allocate more and more unacked_list entries. And the end either causing an out-of-memory situation or increase the management overhead for the (large) list that significant portions of CPU cycles are wasted in searching through the list. When limiting the list to a specific number, it is important to still correctly add a new entry to the list. But if the list became larger than the limit, the last entry of the list (with the highest seqno) must be dropped to still allow the earlier seqnos to finish and therefore to continue the process. Otherwise, the process might get stuck with too high seqnos which are not handled by batadv_tp_ack_unordered().
- Published
- Jul 19, 2026
- Updated
- Aug 17, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
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.
Is your version affected? Check itNoroxi 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.
—
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.8affected
- 33a3bb4a3345bb511f9c69c913da95d4693e2a4e and later · before 31a88792bfba142be3c9521538c1db805677381faffected · git
- 33a3bb4a3345bb511f9c69c913da95d4693e2a4e and later · before 1111a3381bca2d1f084a07686bc783af5ab23df7affected · git
- 33a3bb4a3345bb511f9c69c913da95d4693e2a4e and later · before 1c616b0be4bd8399d485e25e91859373b95d6013affected · git
- 33a3bb4a3345bb511f9c69c913da95d4693e2a4e and later · before f8c499fd275e59203b77fca76ae6ef2d096c2133affected · git
- 33a3bb4a3345bb511f9c69c913da95d4693e2a4e and later · before c6231d628d06d841bc1617b2f7034f5f39876b16affected · git
- 33a3bb4a3345bb511f9c69c913da95d4693e2a4e and later · before 2233787658db859f0a9b83cb397cf783bb8be865affected · git
- 33a3bb4a3345bb511f9c69c913da95d4693e2a4e and later · before 1fb8762600a393d1caccd63be5d07e1756982d68affected · git
- 33a3bb4a3345bb511f9c69c913da95d4693e2a4e and later · before e7c775110e1858e5a7471a23a9c9658c0af9df89affected · git
- before 4.8not 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.177-1 | 6.1.177-1 |
| Debian:13 | linux | before 6.12.95-1 | 6.12.95-1 |
| Debian:14 | linux | before 7.1.3-1 | 7.1.3-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-63819Jul 19, 2026 · f2fs: fix to do sanity check on f2fs_get_node_folio_ra()31Monitor
- ← EarlierCVE-2026-63828Jul 19, 2026 · apparmor: mediate the implicit connect of TCP fast open sendmsg33Monitor
- Later →CVE-2026-63810Jul 19, 2026 · block: Avoid mounting the bdev pseudo-filesystem in userspace0Monitor
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 | 1111a3381bca2d1f084a07686bc783af5ab23df7 | Vendor (CNA) |
| Linux Linux | 1c616b0be4bd8399d485e25e91859373b95d6013 | Vendor (CNA) |
| Linux Linux | 1fb8762600a393d1caccd63be5d07e1756982d68 | Vendor (CNA) |
| Linux Linux | 2233787658db859f0a9b83cb397cf783bb8be865 | Vendor (CNA) |
| Linux Linux | 31a88792bfba142be3c9521538c1db805677381f | Vendor (CNA) |
| Linux Linux | c6231d628d06d841bc1617b2f7034f5f39876b16 | Vendor (CNA) |
| Linux Linux | e7c775110e1858e5a7471a23a9c9658c0af9df89 | Vendor (CNA) |
| Linux Linux | f8c499fd275e59203b77fca76ae6ef2d096c2133 | Vendor (CNA) |
| azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 | 6.6.150.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.177-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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0576 · Jul 20, 2026(Linux Kernel Güvenlik Bildirimi)
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
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 (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/1c616b0be4bd8399d485e25e91859373b95d6013
- git.kernel.org/stable/c/1fb8762600a393d1caccd63be5d07e1756982d68
- git.kernel.org/stable/c/2233787658db859f0a9b83cb397cf783bb8be865
- git.kernel.org/stable/c/31a88792bfba142be3c9521538c1db805677381f
- git.kernel.org/stable/c/c6231d628d06d841bc1617b2f7034f5f39876b16
- git.kernel.org/stable/c/e7c775110e1858e5a7471a23a9c9658c0af9df89
- git.kernel.org/stable/c/f8c499fd275e59203b77fca76ae6ef2d096c2133
Vendor advisories and official records. Exploit/PoC links are deliberately left out.