LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53843: net: openvswitch: reject negative ifindex

In the Linux kernel, the following vulnerability has been resolved: net: openvswitch: reject negative ifindex Recent changes in net-next (commit 759ab1edb56c ("net: store netdevs in an xarray")) refactored the handling of pre-assigned ifindexes and let syzbot surface a latent problem in ovs. ovs does not validate ifindex, making it possible to create netdev ports with negative ifindex values. It's easy to repro with YNL: $ ./cli.py --spec netlink/specs/ovs_datapath.yaml \ --do new \ --json '{"upcall-pid": 1, "name":"my-dp"}' $ ./cli.py --spec netlink/specs/ovs_vport.yaml \ --do new \ --json '{"upcall-pid": "00000001", "name": "some-port0", "dp-ifindex":3,"ifindex":4294901760,"type":2}' $ ip link show -65536: some-port0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 7a:48:21:ad:0b:fb brd ff:ff:ff:ff:ff:ff ... Validate the inputs. Now the second command correctly returns: $ ./cli.py --spec netlink/specs/ovs_vport.yaml \ --do new \ --json '{"upcall-pid": "00000001", "name": "some-port0", "dp-ifindex":3,"ifindex":4294901760,"type":2}' lib.ynl.NlError: Netlink error: Numerical result out of range nl_len = 108 (92) nl_flags = 0x300 nl_type = 2 error: -34 extack: {'msg': 'integer out of range', 'unknown': [[type:4 len:36] b'\x0c\x00\x02\x00\x00\x00\x00\x00\x00\x00\x00\x00\x0c\x00\x03\x00\xff\xff\xff\x7f\x00\x00\x00\x00\x08\x00\x01\x00\x08\x00\x00\x00'], 'bad-attr': '.ifindex'} Accept 0 since it used to be silently ignored.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue lets Open vSwitch accept an invalid negative network interface index. The public record does not describe data theft, privilege escalation, denial of service, or active exploitation. Treat it as a kernel networking correctness issue that matters most where Open vSwitch is enabled.

Executive priority

Track this through normal kernel patch management unless Open vSwitch is business-critical or internet-adjacent. Escalate if vendor advisories later assign impact or exploitation evidence.

Technical view

The Open vSwitch kernel code failed to validate a supplied ifindex when creating netdev ports. After related netdev handling changes, this allowed ports with negative ifindex values. The fix validates inputs, rejects out-of-range negative values, and preserves prior acceptance of zero.

Likely exposure

Likely exposure is limited to affected Linux kernels with Open vSwitch kernel functionality in use. The supplied sources do not state required privileges, remote reachability, or whether default installations are exposed.

Exploitation context

The bundle includes a reproducer, but no public source here states real-world exploitation. KEV is false, and no exploit activity or weaponized abuse is cited.

Researcher notes

Evidence is narrow: invalid ifindex validation in Linux Open vSwitch. No CVSS, CWE, exploit status, or impact chain is provided. Avoid assuming privilege escalation or remote attackability without additional vendor evidence.

Mitigation direction

  • Apply vendor kernel updates that include the referenced stable fixes.
  • Check Linux distribution advisories for exact fixed package versions.
  • Prioritize hosts using Open vSwitch or virtual switching features.
  • If patching is delayed, request vendor-supported compensating guidance.

Validation and detection

  • Inventory Linux kernel versions across systems using Open vSwitch.
  • Confirm whether deployed kernels include the referenced stable commits or backports.
  • Review distribution advisories for CVE-2023-53843 package status.
  • Verify Open vSwitch kernel datapath usage on high-value hosts.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-53843 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux54c4ef34c4b6f9720fded620e2893894f9f2c554, 54c4ef34c4b6f9720fded620e2893894f9f2c554, 54c4ef34c4b6f9720fded620e2893894f9f2c554unaffected
LinuxLinux6.1, 0, 6.1.47, 6.4.12, 6.5affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.