GHSA-5X7P-776C-F64J

Vulnerability from github – Published: 2026-05-01 15:30 – Updated: 2026-05-12 21:31
VLAI?
Details

In the Linux kernel, the following vulnerability has been resolved:

hwmon: (tps53679) Fix array access with zero-length block read

i2c_smbus_read_block_data() can return 0, indicating a zero-length read. When this happens, tps53679_identify_chip() accesses buf[ret - 1] which is buf[-1], reading one byte before the buffer on the stack.

Fix by changing the check from "ret < 0" to "ret <= 0", treating a zero-length read as an error (-EIO), which prevents the out-of-bounds array access.

Also fix a typo in the adjacent comment: "if present" instead of duplicate "if".

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-43005"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-125"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-05-01T15:16:44Z",
    "severity": "HIGH"
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nhwmon: (tps53679) Fix array access with zero-length block read\n\ni2c_smbus_read_block_data() can return 0, indicating a zero-length\nread. When this happens, tps53679_identify_chip() accesses buf[ret - 1]\nwhich is buf[-1], reading one byte before the buffer on the stack.\n\nFix by changing the check from \"ret \u003c 0\" to \"ret \u003c= 0\", treating a\nzero-length read as an error (-EIO), which prevents the out-of-bounds\narray access.\n\nAlso fix a typo in the adjacent comment: \"if present\" instead of\nduplicate \"if\".",
  "id": "GHSA-5x7p-776c-f64j",
  "modified": "2026-05-12T21:31:25Z",
  "published": "2026-05-01T15:30:36Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-43005"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/0e211f6aaa6a00fd0ee0c1eea5498f168c6725e6"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/6999b4769e2a61c463158927102e8c07e3f69ba2"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/79b7e588399bb55f4c10bea6ca41b6c3b944d2bb"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H",
      "type": "CVSS_V3"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…
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.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…