CVE-2026-23103: ipvlan: Make the addrs_lock be per port
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.12% (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 04ba6de6eff61238e5397c14ac26a6578c7735a5, 1f300c10d92c547c3a7d978e1212ff52f18256ed, 3c149b662cbb202a450e81f938e702ba333864ad.
- Severity is disputed: the assigning authority (CNA) scores it 7.8, NVD 5.5.
Low priority for now. Upgrade to Linux Linux 04ba6de6eff61238e5397c14ac26a6578c7735a5, 1f300c10d92c547c3a7d978e1212ff52f18256ed, 3c149b662cbb202a450e81f938e702ba333864ad 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: ipvlan: Make the addrs_lock be per port Make the addrs_lock be per port, not per ipvlan dev. Initial code seems to be written in the assumption, that any address change must occur under RTNL. But it is not so for the case of IPv6. So 1) Introduce per-port addrs_lock. 2) It was needed to fix places where it was forgotten to take lock (ipvlan_open/ipvlan_close) This appears to be a very minor problem though. Since it's highly unlikely that ipvlan_add_addr() will be called on 2 CPU simultaneously. But nevertheless, this could cause: 1) False-negative of ipvlan_addr_busy(): one interface iterated through all port->ipvlans + ipvlan->addrs under some ipvlan spinlock, and another added IP under its own lock. Though this is only possible for IPv6, since looks like only ipvlan_addr6_event() can be called without rtnl_lock. 2) Race since ipvlan_ht_addr_add(port) is called under different ipvlan->addrs_lock locks This should not affect performance, since add/remove IP is a rare situation and spinlock is not taken on fast paths.
- BDU:2026-11576
- ALSA-2026:68531
- ALSA-2026:68532
- ALSA-2026:77689
- ALSA-2026:77690
- openSUSE-SU-2026:20572-1
- RHSA-2026:68531
- RHSA-2026:68532
- RHSA-2026:77689
- RHSA-2026:77690
- RLSA-2026:68531
- RLSA-2026:68532
- RLSA-2026:77689
- RLSA-2026:77690
- SUSE-SU-2026:1342-1
- SUSE-SU-2026:1557-1
- SUSE-SU-2026:1563-1
- SUSE-SU-2026:1573-1
- SUSE-SU-2026:1574-1
- SUSE-SU-2026:1575-1
- Published
- Feb 4, 2026
- Updated
- Nov 10, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- CWE-667
Report tools
Action score
22
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
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 5.5
- CNA · Linux
- 7.8
- 2.3 point gap
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
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.17affected
- 8230819494b3bf284ca7262ac5f877333147b937 and later · before 3c149b662cbb202a450e81f938e702ba333864adaffected · git
- 8230819494b3bf284ca7262ac5f877333147b937 and later · before 70feb16e3fbfb10b15de1396557c38e99f1ab8dfaffected · git
- 8230819494b3bf284ca7262ac5f877333147b937 and later · before 88f83e6c9cdb46b8c8ddd0ba01393362963cf589affected · git
- 8230819494b3bf284ca7262ac5f877333147b937 and later · before 04ba6de6eff61238e5397c14ac26a6578c7735a5affected · git
- 8230819494b3bf284ca7262ac5f877333147b937 and later · before 1f300c10d92c547c3a7d978e1212ff52f18256edaffected · git
- 8230819494b3bf284ca7262ac5f877333147b937 and later · before 6a81e2db096913d7e43aada1c350c1282e76db39affected · git
- 8230819494b3bf284ca7262ac5f877333147b937 and later · before d3ba32162488283c0a4c5bedd8817aec91748802affected · git
- before 4.17not affected · semver
- 5.10.249 and later · up to and including 5.10.*not affected · semver
Affected versions · NVD (7)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel4.17 and later · before 5.10.249
- linux linux kernel5.11 and later · before 5.15.199
- linux linux kernel5.16 and later · before 6.1.162
- linux linux kernel6.2 and later · before 6.6.122
- linux linux kernel6.7 and later · before 6.12.68
- linux linux kernel6.13 and later · before 6.18.8
- linux linux kernel6.19
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | kernel | before 6.12.0-211.64.1.el10_2 | 6.12.0-211.64.1.el10_2 |
| AlmaLinux:10 | kernel-64k | before 6.12.0-211.64.1.el10_2 | 6.12.0-211.64.1.el10_2 |
| AlmaLinux:10 | kernel-64k-core | before 6.12.0-211.64.1.el10_2 | 6.12.0-211.64.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug | before 6.12.0-211.64.1.el10_2 | 6.12.0-211.64.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-core | before 6.12.0-211.64.1.el10_2 | 6.12.0-211.64.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel | before 6.12.0-211.64.1.el10_2 | 6.12.0-211.64.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel-matched | before 6.12.0-211.64.1.el10_2 | 6.12.0-211.64.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules | before 6.12.0-211.64.1.el10_2 | 6.12.0-211.64.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-core | before 6.12.0-211.64.1.el10_2 | 6.12.0-211.64.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-extra | before 6.12.0-211.64.1.el10_2 | 6.12.0-211.64.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel | before 6.12.0-211.64.1.el10_2 | 6.12.0-211.64.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel-matched | before 6.12.0-211.64.1.el10_2 | 6.12.0-211.64.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules | before 6.12.0-211.64.1.el10_2 | 6.12.0-211.64.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-core | before 6.12.0-211.64.1.el10_2 | 6.12.0-211.64.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-extra | before 6.12.0-211.64.1.el10_2 | 6.12.0-211.64.1.el10_2 |
| AlmaLinux:10 | kernel-abi-stablelists | before 6.12.0-211.64.1.el10_2 | 6.12.0-211.64.1.el10_2 |
| AlmaLinux:10 | kernel-core | before 6.12.0-211.64.1.el10_2 | 6.12.0-211.64.1.el10_2 |
| AlmaLinux:10 | kernel-cross-headers | before 6.12.0-211.64.1.el10_2 | 6.12.0-211.64.1.el10_2 |
| AlmaLinux:10 | kernel-debug | before 6.12.0-211.64.1.el10_2 | 6.12.0-211.64.1.el10_2 |
| AlmaLinux:10 | kernel-debug-core | before 6.12.0-211.64.1.el10_2 | 6.12.0-211.64.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel | before 6.12.0-211.64.1.el10_2 | 6.12.0-211.64.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel-matched | before 6.12.0-211.64.1.el10_2 | 6.12.0-211.64.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules | before 6.12.0-211.64.1.el10_2 | 6.12.0-211.64.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules-core | before 6.12.0-211.64.1.el10_2 | 6.12.0-211.64.1.el10_2 |
+96
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-23101Feb 4, 2026 · leds: led-class: Only Add LED to leds_list when it is fully ready18Monitor
- ← EarlierCVE-2026-23102Feb 4, 2026 · arm64/fpsimd: signal: Fix restoration of SVE context28Monitor
- Later →CVE-2026-23104Feb 4, 2026 · ice: fix devlink reload call trace22Monitor
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 | 04ba6de6eff61238e5397c14ac26a6578c7735a5 | Vendor (CNA) |
| Linux Linux | 1f300c10d92c547c3a7d978e1212ff52f18256ed | Vendor (CNA) |
| Linux Linux | 3c149b662cbb202a450e81f938e702ba333864ad | Vendor (CNA) |
| Linux Linux | 6a81e2db096913d7e43aada1c350c1282e76db39 | Vendor (CNA) |
| Linux Linux | 70feb16e3fbfb10b15de1396557c38e99f1ab8df | Vendor (CNA) |
| Linux Linux | 88f83e6c9cdb46b8c8ddd0ba01393362963cf589 | Vendor (CNA) |
| Linux Linux | d3ba32162488283c0a4c5bedd8817aec91748802 | Vendor (CNA) |
| almalinux:bpftool | 4.18.0-553.164.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel | 4.18.0-553.164.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-abi-stablelists | 4.18.0-553.164.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-core | 4.18.0-553.164.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-cross-headers | 4.18.0-553.164.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug | 4.18.0-553.164.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-core | 4.18.0-553.164.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-devel | 4.18.0-553.164.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-modules | 4.18.0-553.164.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-modules-extra | 4.18.0-553.164.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-devel | 4.18.0-553.164.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-doc | 4.18.0-553.164.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| debian:linux | 6.1.162-1 · Debian:12 | Package registry (OSV) |
| opensuse:dtb-aarch64 | 6.12.0-160000.28.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-64kb | 6.12.0-160000.28.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-azure | 6.12.0-160000.28.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-default | 6.12.0-160000.28.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-default-base | 6.12.0-160000.27.1.160000.2.8 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-docs | 6.12.0-160000.28.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-kvmsmall | 6.12.0-160000.28.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-obs-build | 6.12.0-160000.28.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-obs-qa | 6.12.0-160000.28.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-rt | 6.12.0-160000.28.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
+28
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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
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-667 · Improper LockingCVSS 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.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- git.kernel.org/stable/c/1f300c10d92c547c3a7d978e1212ff52f18256ed
- git.kernel.org/stable/c/3c149b662cbb202a450e81f938e702ba333864ad
- git.kernel.org/stable/c/6a81e2db096913d7e43aada1c350c1282e76db39
- git.kernel.org/stable/c/70feb16e3fbfb10b15de1396557c38e99f1ab8df
- git.kernel.org/stable/c/88f83e6c9cdb46b8c8ddd0ba01393362963cf589
- git.kernel.org/stable/c/d3ba32162488283c0a4c5bedd8817aec91748802
- cert-portal.siemens.com/productcert/html/ssa-019113.html
- cert-portal.siemens.com/productcert/html/ssa-457936.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.