CVE-2026-23103ipvlan: Make the addrs_lock be per port
Updated under an hour ago ()
Does this affect you?
It affects Linux and 4 other products. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- 7.8 HIGH (v3.1, CNA)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Modified
- Record last updated
- Oct 15, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | 8230819494b3bf284ca7262ac5f877333147b937 builds before 3c149b662cbb202a450e81f938e702ba333864ad; 8230819494b3bf284ca7262ac5f877333147b937 builds before 70feb16e3fbfb10b15de1396557c38e99f1ab8df; 8230819494b3bf284ca7262ac5f877333147b937 builds before 88f83e6c9cdb46b8c8ddd0ba01393362963cf589; 8230819494b3bf284ca7262ac5f877333147b937 builds before 04ba6de6eff61238e5397c14ac26a6578c7735a5; 8230819494b3bf284ca7262ac5f877333147b937 builds before 1f300c10d92c547c3a7d978e1212ff52f18256ed; 8230819494b3bf284ca7262ac5f877333147b937 builds before 6a81e2db096913d7e43aada1c350c1282e76db39; from 8230819494b3bf284ca7262ac5f877333147b937 before d3ba32162488283c0a4c5bedd8817aec91748802 | CNA record |
Siemens SIMATIC S7-1500 CPU 1518-4 PN/DP MFP siemens:simatic_s7_1500_cpu_1518_4_pn_dp_mfp (from the name) | from V3.1.6 | CISA ADP |
Siemens SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP siemens:simatic_s7_1500_cpu_1518f_4_pn_dp_mfp (from the name) | from V3.1.6 | CISA ADP |
Siemens SIPLUS S7-1500 CPU 1518-4 PN/DP MFP siemens:siplus_s7_1500_cpu_1518_4_pn_dp_mfp (from the name) | from V3.1.6 | CISA ADP |
linux linux_kernel linux:linux_kernel | from 4.17 before 5.10.249; from 5.11 before 5.15.199; from 5.16 before 6.1.162; from 6.2 before 6.6.122; from 6.7 before 6.12.68; from 6.13 before 6.18.8; 6.19; 6.19; and 4 more ranges | NVD |
References
- https://git.kernel.org/stable/c/3c149b662cbb202a450e81f938e702ba333864adpatch
- https://git.kernel.org/stable/c/70feb16e3fbfb10b15de1396557c38e99f1ab8dfpatch
- https://git.kernel.org/stable/c/88f83e6c9cdb46b8c8ddd0ba01393362963cf589patch
- https://git.kernel.org/stable/c/04ba6de6eff61238e5397c14ac26a6578c7735a5patch
- https://git.kernel.org/stable/c/1f300c10d92c547c3a7d978e1212ff52f18256edpatch
- https://git.kernel.org/stable/c/6a81e2db096913d7e43aada1c350c1282e76db39patch
- https://git.kernel.org/stable/c/d3ba32162488283c0a4c5bedd8817aec91748802patch
- https://cert-portal.siemens.com/productcert/html/ssa-019113.html
- https://cert-portal.siemens.com/productcert/html/ssa-457936.html
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.