LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53066: qed/qed_sriov: guard against NULL derefs from qed_iov_get_vf_info

In the Linux kernel, the following vulnerability has been resolved: qed/qed_sriov: guard against NULL derefs from qed_iov_get_vf_info We have to make sure that the info returned by the helper is valid before using it. Found by Linux Verification Center (linuxtesting.org) with the SVACE static analysis tool.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2023-53066 is a Linux kernel bug in the qed SR-IOV driver path where code could use missing VF information and dereference NULL. The public record does not provide a CVSS score or confirmed impact, but kernel NULL dereferences usually matter because they can crash affected systems or driver paths.

Executive priority

Treat this as a targeted infrastructure hygiene item, not an emergency, unless critical virtualization or network hosts use qed SR-IOV and cannot be patched quickly.

Technical view

The fix adds validation around data returned by qed_iov_get_vf_info before it is used in qed/qed_sriov. The issue was found by static analysis from the Linux Verification Center using SVACE. The source bundle identifies Linux kernel versions and stable commits, but does not describe a trigger, privilege boundary, or complete impact.

Likely exposure

Exposure is most likely on Linux systems running affected kernel versions with the qed driver and SR-IOV virtual function management in use. Systems not using this driver or SR-IOV path are less likely to be exposed, based on the limited source detail.

Exploitation context

The CVE is not marked KEV, and the provided sources do not claim active exploitation or public exploit availability. Evidence only supports a NULL dereference class issue fixed in Linux stable commits.

Researcher notes

The record lacks CVSS, CWE, exploitability details, and a precise attacker model. Analysis should focus on code reachability in qed SR-IOV VF handling and whether local, guest, or device-driven inputs can make qed_iov_get_vf_info return NULL.

Mitigation direction

  • Review vendor Linux kernel advisories for packages containing the referenced stable fixes.
  • Prioritize kernel updates on hosts using qed network drivers with SR-IOV enabled.
  • If immediate patching is blocked, assess whether qed SR-IOV usage can be reduced safely.
  • Track distribution backports instead of relying only on upstream kernel version strings.

Validation and detection

  • Inventory Linux kernels and identify systems using the qed driver.
  • Check whether SR-IOV is enabled on relevant network adapters.
  • Compare installed kernel packages against vendor advisories and fixed stable releases.
  • Confirm the relevant upstream or distro backport patch is present.
Prepared
Confidence
medium
Sources
10

Public sources used

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-53066 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
9Source 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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux733def6a04bf3d2810dd675e1240f8df94d633c3, 733def6a04bf3d2810dd675e1240f8df94d633c3, 733def6a04bf3d2810dd675e1240f8df94d633c3, 733def6a04bf3d2810dd675e1240f8df94d633c3, 733def6a04bf3d2810dd675e1240f8df94d633c3, 733def6a04bf3d2810dd675e1240f8df94d633c3, 733def6a04bf3d2810dd675e1240f8df94d633c3, 733def6a04bf3d2810dd675e1240f8df94d633c3unaffected
LinuxLinux4.7, 0, 4.14.312, 4.19.280, 5.4.240, 5.10.177, 5.15.105, 6.1.22, 6.2.9, 6.3affected
Weakness

CWE details

No CWE listed

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