---
id: CVE-2026-23103
title: |-
  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 chan…
summary: |-
  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 chan…
severity: high
cvss: 7.8
cvssVector: 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'
cwe:
  - CWE-667
  - CWE-413
vendor: linux
product: linux_kernel
affected:
  - 'linux_kernel >= 4.17, < 5.10.249'
  - 'linux_kernel >= 5.11, < 5.15.199'
  - 'linux_kernel >= 5.16, < 6.1.162'
  - 'linux_kernel >= 6.2, < 6.6.122'
  - 'linux_kernel >= 6.7, < 6.12.68'
  - 'linux_kernel >= 6.13, < 6.18.8'
  - linux_kernel = 6.19
patched:
  - linux_kernel 6.18.8
published: '2026-02-04'
updated: '2026-10-15'
sourceUpdated: '2026-10-15T02:18:42.237'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-23103'
references:
  - url: 'https://git.kernel.org/stable/c/04ba6de6eff61238e5397c14ac26a6578c7735a5'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/1f300c10d92c547c3a7d978e1212ff52f18256ed'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/3c149b662cbb202a450e81f938e702ba333864ad'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/6a81e2db096913d7e43aada1c350c1282e76db39'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/70feb16e3fbfb10b15de1396557c38e99f1ab8df'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/88f83e6c9cdb46b8c8ddd0ba01393362963cf589'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/d3ba32162488283c0a4c5bedd8817aec91748802'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://cert-portal.siemens.com/productcert/html/ssa-019113.html'
    label: 0b142b55-0307-4c5a-b3c9-f314f3fb7c5e
  - url: 'https://cert-portal.siemens.com/productcert/html/ssa-457936.html'
    label: 0b142b55-0307-4c5a-b3c9-f314f3fb7c5e
  - url: >-
      https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-23103.json
  - url: 'https://access.redhat.com/security/cve/CVE-2026-23103'
  - url: 'https://bugzilla.redhat.com/show_bug.cgi?id=2436771'
  - url: 'https://www.cve.org/CVERecord?id=CVE-2026-23103'
  - url: 'https://nvd.nist.gov/vuln/detail/CVE-2026-23103'
  - url: >-
      https://lore.kernel.org/linux-cve-announce/2026020429-CVE-2026-23103-63b3@gregkh/T
  - url: 'https://access.redhat.com/errata/RHSA-2026:68531'
  - url: 'https://access.redhat.com/errata/RHSA-2026:68532'
tags:
  - nvd
  - csaf
  - vex
  - red-hat
  - cve.org
  - score-dispute
epss: 0.00125
epssPercentile: 0.02214
ssvc:
  exploitation: none
  automatable: 'no'
  technicalImpact: total
  timestamp: '2026-06-16T20:21:03.730200Z'
scores:
  nvd: 7.8
  vendor: 4.7
  cna: 7.8
ingestedAt: '2026-09-08T15:33:26.993Z'
---

## Overview

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.

## Affected

- `linux_kernel >= 4.17, < 5.10.249`
- `linux_kernel >= 5.11, < 5.15.199`
- `linux_kernel >= 5.16, < 6.1.162`
- `linux_kernel >= 6.2, < 6.6.122`
- `linux_kernel >= 6.7, < 6.12.68`
- `linux_kernel >= 6.13, < 6.18.8`
- `linux_kernel = 6.19`

## Remediation

Upgrade past the affected range:

- `linux_kernel 6.18.8`

## Vendor advisories

- **RHSA-2026:68531** · Red Hat · fixed in: Red Hat Enterprise Linux BaseOS (v. 8), Red Hat Enterprise Linux CRB (v. 8) · released 2026-09-17 · [advisory](https://access.redhat.com/errata/RHSA-2026:68531)
- **RHSA-2026:68532** · Red Hat · fixed in: Red Hat Enterprise Linux NFV (v. 8), Red Hat Enterprise Linux RT (v. 8) · released 2026-09-17 · [advisory](https://access.redhat.com/errata/RHSA-2026:68532)
- **Red Hat VEX** · Moderate · affected: Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 9 · no fix planned: Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 9 · updated 2026-09-17 · [vex](https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-23103.json)