CVE-2026-23103

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.

PUBLISHED Reserved 2026-01-13 | Published 2026-02-04 | Updated 2026-02-09 | Assigner Linux

Product status

References

git.kernel.org/...c/3c149b662cbb202a450e81f938e702ba333864ad

git.kernel.org/...c/70feb16e3fbfb10b15de1396557c38e99f1ab8df

git.kernel.org/...c/88f83e6c9cdb46b8c8ddd0ba01393362963cf589

git.kernel.org/...c/04ba6de6eff61238e5397c14ac26a6578c7735a5

git.kernel.org/...c/1f300c10d92c547c3a7d978e1212ff52f18256ed

git.kernel.org/...c/6a81e2db096913d7e43aada1c350c1282e76db39

git.kernel.org/...c/d3ba32162488283c0a4c5bedd8817aec91748802

cve.org (CVE-2026-23103)

nvd.nist.gov (CVE-2026-23103)

Download JSON