GHSA-3MJW-95XR-9726

Vulnerability from github – Published: 2026-07-01 15:35 – Updated: 2026-07-01 15:35
VLAI
Details

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

i2c: qcom-cci: Fix NULL pointer dereference in cci_remove()

On all modern platforms Qualcomm CCI controller provides two I2C masters, and on particular boards only one I2C master may be initialized, and in such cases the device unbinding or driver removal causes a NULL pointer dereference, because cci_halt() is called for all two I2C masters, but a completion is initialized only for the single enabled master:

% rmmod i2c-qcom-cci
Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000
<snip>
Call trace:
__wait_for_common+0x194/0x1a8 (P)
wait_for_completion_timeout+0x20/0x2c
cci_remove+0xc4/0x138 [i2c_qcom_cci]
platform_remove+0x20/0x30
device_remove+0x4c/0x80
device_release_driver_internal+0x1c8/0x224
driver_detach+0x50/0x98
bus_remove_driver+0x6c/0xbc
driver_unregister+0x30/0x60
platform_driver_unregister+0x14/0x20
qcom_cci_driver_exit+0x18/0x1008 [i2c_qcom_cci]
....
Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2026-53339"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-07-01T14:16:41Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\ni2c: qcom-cci: Fix NULL pointer dereference in cci_remove()\n\nOn all modern platforms Qualcomm CCI controller provides two I2C masters,\nand on particular boards only one I2C master may be initialized, and in\nsuch cases the device unbinding or driver removal causes a NULL pointer\ndereference, because cci_halt() is called for all two I2C masters, but\na completion is initialized only for the single enabled master:\n\n    % rmmod i2c-qcom-cci\n    Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000\n    \u003csnip\u003e\n    Call trace:\n    __wait_for_common+0x194/0x1a8 (P)\n    wait_for_completion_timeout+0x20/0x2c\n    cci_remove+0xc4/0x138 [i2c_qcom_cci]\n    platform_remove+0x20/0x30\n    device_remove+0x4c/0x80\n    device_release_driver_internal+0x1c8/0x224\n    driver_detach+0x50/0x98\n    bus_remove_driver+0x6c/0xbc\n    driver_unregister+0x30/0x60\n    platform_driver_unregister+0x14/0x20\n    qcom_cci_driver_exit+0x18/0x1008 [i2c_qcom_cci]\n    ....",
  "id": "GHSA-3mjw-95xr-9726",
  "modified": "2026-07-01T15:35:19Z",
  "published": "2026-07-01T15:35:19Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-53339"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/4cd206c1d57a9370d5219f7b1fc45169d7bdf951"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/4d2b4a9cda6837e5ee1de1290f2e773a713b71e9"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/7107627b8b35015027201e7a095a3f6e30b4a46f"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/729ac5a4b966aac42e08a94dea966f4429008548"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/8ce7ff721a5e9d06d53ef65d01c89fce6d26d6ff"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/a162a260c8c4db7501c65220e76913e8e351f823"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/a50b8adb9cdb9a495b0b45583956897b7411ed7a"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/e8669d12da0ade52adfe0abe96cd99e708abc9bd"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





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.


Detection rules are retrieved from Rulezet.