OESA-2026-3244 (CVE-2026-16313)

Vulnerability from osv_openeuler – Published: 2026-08-07 02:41 – Updated: 2026-08-07 02:41 – Source website
VLAI
Summary
sg3_utils security update
Details

The sg3_utils package contains utilities that send SCSI commands to devices. As well as devices on transports traditionally associated with SCSI (e.g. Fibre Channel (FCP), Serial Attached SCSI (SAS) and the SCSI Parallel Interface(SPI)) many other devices use SCSI command sets. ATAPI cd/dvd drives and SATA disks that connect via a translation layer or a bridge device are examples of devices that use SCSI command sets.

Security Fix(es):

A flaw was found in sg3_utils. The sg_inq command, when invoked with the --export option, outputs device identification data without sanitizing control characters in SCSI name string fields. A newline character embedded in a device-supplied name string can inject arbitrary properties into the udev device database. This could allow an attacker who can present a crafted SCSI device to execute arbitrary commands as root when the device is disconnected.(CVE-2026-16313)


{
  "affected": [
    {
      "ecosystem_specific": {
        "aarch64": [
          "sg3_utils-1.48-4.oe2403sp3.aarch64.rpm",
          "sg3_utils-debuginfo-1.48-4.oe2403sp3.aarch64.rpm",
          "sg3_utils-debugsource-1.48-4.oe2403sp3.aarch64.rpm",
          "sg3_utils-devel-1.48-4.oe2403sp3.aarch64.rpm",
          "sg3_utils-help-1.48-4.oe2403sp3.aarch64.rpm"
        ],
        "src": [
          "sg3_utils-1.48-4.oe2403sp3.src.rpm"
        ],
        "x86_64": [
          "sg3_utils-1.48-4.oe2403sp3.x86_64.rpm",
          "sg3_utils-debuginfo-1.48-4.oe2403sp3.x86_64.rpm",
          "sg3_utils-debugsource-1.48-4.oe2403sp3.x86_64.rpm",
          "sg3_utils-devel-1.48-4.oe2403sp3.x86_64.rpm",
          "sg3_utils-help-1.48-4.oe2403sp3.x86_64.rpm"
        ]
      },
      "package": {
        "ecosystem": "openEuler:24.03-LTS-SP3",
        "name": "sg3_utils",
        "purl": "pkg:rpm/openEuler/sg3_utils\u0026distro=openEuler-24.03-LTS-SP3"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.48-4.oe2403sp3"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "aarch64": [
          "sg3_utils-1.48-4.oe2403sp4.aarch64.rpm",
          "sg3_utils-debuginfo-1.48-4.oe2403sp4.aarch64.rpm",
          "sg3_utils-debugsource-1.48-4.oe2403sp4.aarch64.rpm",
          "sg3_utils-devel-1.48-4.oe2403sp4.aarch64.rpm",
          "sg3_utils-help-1.48-4.oe2403sp4.aarch64.rpm"
        ],
        "src": [
          "sg3_utils-1.48-4.oe2403sp4.src.rpm"
        ],
        "x86_64": [
          "sg3_utils-1.48-4.oe2403sp4.x86_64.rpm",
          "sg3_utils-debuginfo-1.48-4.oe2403sp4.x86_64.rpm",
          "sg3_utils-debugsource-1.48-4.oe2403sp4.x86_64.rpm",
          "sg3_utils-devel-1.48-4.oe2403sp4.x86_64.rpm",
          "sg3_utils-help-1.48-4.oe2403sp4.x86_64.rpm"
        ]
      },
      "package": {
        "ecosystem": "openEuler:24.03-LTS-SP4",
        "name": "sg3_utils",
        "purl": "pkg:rpm/openEuler/sg3_utils\u0026distro=openEuler-24.03-LTS-SP4"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.48-4.oe2403sp4"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "aarch64": [
          "sg3_utils-1.45-14.oe2003sp4.aarch64.rpm",
          "sg3_utils-debuginfo-1.45-14.oe2003sp4.aarch64.rpm",
          "sg3_utils-debugsource-1.45-14.oe2003sp4.aarch64.rpm",
          "sg3_utils-devel-1.45-14.oe2003sp4.aarch64.rpm",
          "sg3_utils-help-1.45-14.oe2003sp4.aarch64.rpm"
        ],
        "src": [
          "sg3_utils-1.45-14.oe2003sp4.src.rpm"
        ],
        "x86_64": [
          "sg3_utils-1.45-14.oe2003sp4.x86_64.rpm",
          "sg3_utils-debuginfo-1.45-14.oe2003sp4.x86_64.rpm",
          "sg3_utils-debugsource-1.45-14.oe2003sp4.x86_64.rpm",
          "sg3_utils-devel-1.45-14.oe2003sp4.x86_64.rpm",
          "sg3_utils-help-1.45-14.oe2003sp4.x86_64.rpm"
        ]
      },
      "package": {
        "ecosystem": "openEuler:20.03-LTS-SP4",
        "name": "sg3_utils",
        "purl": "pkg:rpm/openEuler/sg3_utils\u0026distro=openEuler-20.03-LTS-SP4"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.45-14.oe2003sp4"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "aarch64": [
          "sg3_utils-1.46-10.oe2203sp4.aarch64.rpm",
          "sg3_utils-debuginfo-1.46-10.oe2203sp4.aarch64.rpm",
          "sg3_utils-debugsource-1.46-10.oe2203sp4.aarch64.rpm",
          "sg3_utils-devel-1.46-10.oe2203sp4.aarch64.rpm",
          "sg3_utils-help-1.46-10.oe2203sp4.aarch64.rpm"
        ],
        "src": [
          "sg3_utils-1.46-10.oe2203sp4.src.rpm"
        ],
        "x86_64": [
          "sg3_utils-1.46-10.oe2203sp4.x86_64.rpm",
          "sg3_utils-debuginfo-1.46-10.oe2203sp4.x86_64.rpm",
          "sg3_utils-debugsource-1.46-10.oe2203sp4.x86_64.rpm",
          "sg3_utils-devel-1.46-10.oe2203sp4.x86_64.rpm",
          "sg3_utils-help-1.46-10.oe2203sp4.x86_64.rpm"
        ]
      },
      "package": {
        "ecosystem": "openEuler:22.03-LTS-SP4",
        "name": "sg3_utils",
        "purl": "pkg:rpm/openEuler/sg3_utils\u0026distro=openEuler-22.03-LTS-SP4"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.46-10.oe2203sp4"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "aarch64": [
          "sg3_utils-1.48-4.oe2403sp1.aarch64.rpm",
          "sg3_utils-debuginfo-1.48-4.oe2403sp1.aarch64.rpm",
          "sg3_utils-debugsource-1.48-4.oe2403sp1.aarch64.rpm",
          "sg3_utils-devel-1.48-4.oe2403sp1.aarch64.rpm",
          "sg3_utils-help-1.48-4.oe2403sp1.aarch64.rpm"
        ],
        "src": [
          "sg3_utils-1.48-4.oe2403sp1.src.rpm"
        ],
        "x86_64": [
          "sg3_utils-1.48-4.oe2403sp1.x86_64.rpm",
          "sg3_utils-debuginfo-1.48-4.oe2403sp1.x86_64.rpm",
          "sg3_utils-debugsource-1.48-4.oe2403sp1.x86_64.rpm",
          "sg3_utils-devel-1.48-4.oe2403sp1.x86_64.rpm",
          "sg3_utils-help-1.48-4.oe2403sp1.x86_64.rpm"
        ]
      },
      "package": {
        "ecosystem": "openEuler:24.03-LTS-SP1",
        "name": "sg3_utils",
        "purl": "pkg:rpm/openEuler/sg3_utils\u0026distro=openEuler-24.03-LTS-SP1"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.48-4.oe2403sp1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "database_specific": {
    "severity": "High"
  },
  "details": "The sg3_utils package contains utilities that send SCSI commands to devices. As well as devices on transports traditionally associated with SCSI (e.g. Fibre Channel (FCP), Serial Attached SCSI (SAS) and the SCSI Parallel Interface(SPI)) many other devices use SCSI command sets. ATAPI cd/dvd drives and SATA disks that connect via a translation layer or a bridge device are examples of devices that use SCSI command sets.\r\n\r\nSecurity Fix(es):\n\nA flaw was found in sg3_utils. The sg_inq command, when invoked with the --export option, outputs device identification data without sanitizing control characters in SCSI name string fields. A newline character embedded in a device-supplied name string can inject arbitrary properties into the udev device database. This could allow an attacker who can present a crafted SCSI device to execute arbitrary commands as root when the device is disconnected.(CVE-2026-16313)",
  "id": "OESA-2026-3244",
  "modified": "2026-08-07T02:41:42Z",
  "published": "2026-08-07T02:41:42Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-3244"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-16313"
    }
  ],
  "schema_version": "1.7.2",
  "severity": [
    {
      "score": "CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "sg3_utils security update",
  "upstream": [
    "CVE-2026-16313"
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.