Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

MediumCVSS 5.5 · v3.1—No exploit Fix available

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.

Published
Feb 4, 2026
Updated
Nov 10, 2026
EPSS
0.1% · 2th percentile

Report tools

JSON

Action score

22

Monitor

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.

Follow CVE-2026-23103

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi 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 help

Affected 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.

VendorProduct
linuxlinux 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

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernelbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64kbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-corebefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-debugbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-modulesbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-modules-corebefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-modules-extrabefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-corebefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-cross-headersbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-debugbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-debug-corebefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-debug-modulesbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-debug-modules-corebefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • 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…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

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 ready
    18Monitor
  • ← EarlierCVE-2026-23102Feb 4, 2026 · arm64/fpsimd: signal: Fix restoration of SVE context
    28Monitor
  • Later →CVE-2026-23104Feb 4, 2026 · ice: fix devlink reload call trace
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux04ba6de6eff61238e5397c14ac26a6578c7735a5Vendor (CNA)
Linux Linux1f300c10d92c547c3a7d978e1212ff52f18256edVendor (CNA)
Linux Linux3c149b662cbb202a450e81f938e702ba333864adVendor (CNA)
Linux Linux6a81e2db096913d7e43aada1c350c1282e76db39Vendor (CNA)
Linux Linux70feb16e3fbfb10b15de1396557c38e99f1ab8dfVendor (CNA)
Linux Linux88f83e6c9cdb46b8c8ddd0ba01393362963cf589Vendor (CNA)
Linux Linuxd3ba32162488283c0a4c5bedd8817aec91748802Vendor (CNA)
almalinux:bpftool4.18.0-553.164.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel4.18.0-553.164.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-abi-stablelists4.18.0-553.164.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-core4.18.0-553.164.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-cross-headers4.18.0-553.164.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug4.18.0-553.164.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-core4.18.0-553.164.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-devel4.18.0-553.164.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules4.18.0-553.164.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules-extra4.18.0-553.164.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-devel4.18.0-553.164.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-doc4.18.0-553.164.1.el8_10 · AlmaLinux:8Package registry (OSV)
debian:linux6.1.162-1 · Debian:12Package registry (OSV)
opensuse:dtb-aarch646.12.0-160000.28.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-64kb6.12.0-160000.28.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-azure6.12.0-160000.28.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-default6.12.0-160000.28.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-default-base6.12.0-160000.27.1.160000.2.8 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-docs6.12.0-160000.28.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-kvmsmall6.12.0-160000.28.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-obs-build6.12.0-160000.28.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-obs-qa6.12.0-160000.28.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-rt6.12.0-160000.28.1 · openSUSE:Leap 16.0Package 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 Locking

CVSS 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.

References

All records