CVE-2026-23103
Last modified
CVE-2026-23103 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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. EPSS estimates a 0.11% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 4.17, < 5.10.249 | — |
| Linux | Linux Kernel | >= 5.11, < 5.15.199 | — |
| Linux | Linux Kernel | >= 5.16, < 6.1.162 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.122 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.68 | — |
| Linux | Linux Kernel | >= 6.13, < 6.18.8 | — |
| Linux | Linux Kernel | 6.19 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2026-23103?
How severe is CVE-2026-23103?
How do I fix CVE-2026-23103?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-23097In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23098In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-23099In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-23100In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23101In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2026-23102In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-23104In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23105In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23106In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23107In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23108In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23109In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2026-23103?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
