CVE-2026-23286: atm: lec: fix null-ptr-deref in lec_arp_clear_vccs
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.13% (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 101bacb303e89dc2e0640ae6a5e0fb97c4eb45bb, 2d9f57ea29a1f1772373b98a509b44d49fda609e, 30c9744a989feb22cfbb84170eb0e038a7a2c1da; azl3 kernel 6.6.126.1-1 on Azure Linux 3.0 6.6.130.1-1.
Low priority for now. Upgrade to Linux Linux 101bacb303e89dc2e0640ae6a5e0fb97c4eb45bb, 2d9f57ea29a1f1772373b98a509b44d49fda609e, 30c9744a989feb22cfbb84170eb0e038a7a2c1da; azl3 kernel 6.6.126.1-1 on Azure Linux 3.0 6.6.130.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: atm: lec: fix null-ptr-deref in lec_arp_clear_vccs syzkaller reported a null-ptr-deref in lec_arp_clear_vccs(). This issue can be easily reproduced using the syzkaller reproducer. In the ATM LANE (LAN Emulation) module, the same atm_vcc can be shared by multiple lec_arp_table entries (e.g., via entry->vcc or entry->recv_vcc). When the underlying VCC is closed, lec_vcc_close() iterates over all ARP entries and calls lec_arp_clear_vccs() for each matched entry. For example, when lec_vcc_close() iterates through the hlists in priv->lec_arp_empty_ones or other ARP tables: 1. In the first iteration, for the first matched ARP entry sharing the VCC, lec_arp_clear_vccs() frees the associated vpriv (which is vcc->user_back) and sets vcc->user_back to NULL. 2. In the second iteration, for the next matched ARP entry sharing the same VCC, lec_arp_clear_vccs() is called again. It obtains a NULL vpriv from vcc->user_back (via LEC_VCC_PRIV(vcc)) and then attempts to dereference it via `vcc->pop = vpriv->old_pop`, leading to a null-ptr-deref crash. Fix this by adding a null check for vpriv before dereferencing it. If vpriv is already NULL, it means the VCC has been cleared by a previous call, so we can safely skip the cleanup and just clear the entry's vcc/recv_vcc pointers. The entire cleanup block (including vcc_release_async()) is placed inside the vpriv guard because a NULL vpriv indicates the VCC has already been fully released by a prior iteration — repeating the teardown would redundantly set flags and trigger callbacks on an already-closing socket. The Fixes tag points to the initial commit because the entry->vcc path has been vulnerable since the original code. The entry->recv_vcc path was later added by commit 8d9f73c0ad2f ("atm: fix a memory leak of vcc->user_back") with the same pattern, and both paths are fixed here.
- Published
- Mar 25, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- CWE-476
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%
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 kernel2.6.12.1 and later · before 5.10.253
- linux linux kernel5.11 and later · before 5.15.203
- linux linux kernel5.16 and later · before 6.1.167
- linux linux kernel6.2 and later · before 6.6.130
- linux linux kernel6.7 and later · before 6.12.77
- linux linux kernel6.13 and later · before 6.18.17
- linux linux kernel6.19 and later · before 6.19.7
- linux linux kernel2.6.12
- linux linux kernel7.0
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
- 2.6.12affected
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 8aff65a82b6389ec674d46e5b3d3ae6f07db5e3eaffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 30c9744a989feb22cfbb84170eb0e038a7a2c1daaffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before e9665986eb127290ceb535bd5d04d7a84265d94faffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 622062f24644b4536d3f437e0cf7a8c4bb421665affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 2d9f57ea29a1f1772373b98a509b44d49fda609eaffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 7ea92ab075d809ec8a96669a5ecf00f752057875affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 5f1cfea7921f5c126a441d973690eeba52677b64affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 101bacb303e89dc2e0640ae6a5e0fb97c4eb45bbaffected · git
- before 2.6.12not 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.170-1 | 6.1.170-1 |
| Debian:13 | linux | before 6.12.85-1 | 6.12.85-1 |
| Debian:14 | linux | before 6.19.8-1 | 6.19.8-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-2026-23283Mar 25, 2026 · regulator: fp9931: Fix PM runtime reference leak in fp9931_hwmon_read()22Monitor
- ← EarlierCVE-2026-23285Mar 25, 2026 · drbd: fix null-pointer dereference on local read error22Monitor
- Later →CVE-2026-23288Mar 25, 2026 · accel/amdxdna: Fix out-of-bounds memset in command slot handling31Monitor
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 | 101bacb303e89dc2e0640ae6a5e0fb97c4eb45bb | Vendor (CNA) |
| Linux Linux | 2d9f57ea29a1f1772373b98a509b44d49fda609e | Vendor (CNA) |
| Linux Linux | 30c9744a989feb22cfbb84170eb0e038a7a2c1da | Vendor (CNA) |
| Linux Linux | 5f1cfea7921f5c126a441d973690eeba52677b64 | Vendor (CNA) |
| Linux Linux | 622062f24644b4536d3f437e0cf7a8c4bb421665 | Vendor (CNA) |
| Linux Linux | 7ea92ab075d809ec8a96669a5ecf00f752057875 | Vendor (CNA) |
| Linux Linux | 8aff65a82b6389ec674d46e5b3d3ae6f07db5e3e | Vendor (CNA) |
| Linux Linux | e9665986eb127290ceb535bd5d04d7a84265d94f | Vendor (CNA) |
| azl3 kernel 6.6.126.1-1 on Azure Linux 3.0 | 6.6.130.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.170-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).
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)
CWE-476 · NULL Pointer DereferenceCVSS 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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/2d9f57ea29a1f1772373b98a509b44d49fda609e
- git.kernel.org/stable/c/30c9744a989feb22cfbb84170eb0e038a7a2c1da
- git.kernel.org/stable/c/5f1cfea7921f5c126a441d973690eeba52677b64
- git.kernel.org/stable/c/622062f24644b4536d3f437e0cf7a8c4bb421665
- git.kernel.org/stable/c/7ea92ab075d809ec8a96669a5ecf00f752057875
- git.kernel.org/stable/c/8aff65a82b6389ec674d46e5b3d3ae6f07db5e3e
- git.kernel.org/stable/c/e9665986eb127290ceb535bd5d04d7a84265d94f
Vendor advisories and official records. Exploit/PoC links are deliberately left out.