Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-23103ipvlan: Make the addrs_lock be per port

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.

Timeline

  1. ID reserved

    By Linux

  2. · 22 days later

    Published

  3. · 9 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-23103, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.13% · top 97% of all CVEs (19 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 8230819494b3bf284ca7262ac5f877333147b937 – < 3c149b662cbb202a450e81f938e702ba333864ad
    • affected 8230819494b3bf284ca7262ac5f877333147b937 – < 70feb16e3fbfb10b15de1396557c38e99f1ab8df
    • affected 8230819494b3bf284ca7262ac5f877333147b937 – < 88f83e6c9cdb46b8c8ddd0ba01393362963cf589
    • affected 8230819494b3bf284ca7262ac5f877333147b937 – < 04ba6de6eff61238e5397c14ac26a6578c7735a5
    • affected 8230819494b3bf284ca7262ac5f877333147b937 – < 1f300c10d92c547c3a7d978e1212ff52f18256ed
    • affected 8230819494b3bf284ca7262ac5f877333147b937 – < 6a81e2db096913d7e43aada1c350c1282e76db39
    • affected 8230819494b3bf284ca7262ac5f877333147b937 – < d3ba32162488283c0a4c5bedd8817aec91748802
  • Linux · Linux

    • affected 4.17
    • unaffected < 4.17
    • unaffected 5.10.249 – ≤ 5.10.*
    • unaffected 5.15.199 – ≤ 5.15.*
    • unaffected 6.1.162 – ≤ 6.1.*
    • unaffected 6.6.122 – ≤ 6.6.*
    • unaffected 6.12.68 – ≤ 6.12.*
    • unaffected 6.18.8 – ≤ 6.18.*
    • unaffected 6.19 – ≤ *

References

References9

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-23103 badge
[![CVE-2026-23103](https://cveledger.app/badge/CVE-2026-23103.svg)](https://cveledger.app/cve/CVE-2026-23103)

Record last updated .