{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-97502 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-97502 is a vulnerability in Linux, published on 24 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-97502 and fix it if it is affected.\n\nWhat it is: CVE-2026-97502 is a vulnerability in Linux, published on 24 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-97502 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-97502/ (Markdown: https://insights.sbomify.com/CVE-2026-97502/index.md)","id":"CVE-2026-97502","markdown":"https://insights.sbomify.com/CVE-2026-97502/index.md","name":"CVE-2026-97502","record":{"aliases":["AZL-103793","BELL-CVE-2026-97502","DEBIAN-CVE-2026-97502","GHSA-7j63-m3c7-g76r","UBUNTU-CVE-2026-97502"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A NULL pointer dereference in the Linux kernel's Davinci MMC driver IRQ handler allows local attackers to cause a system crash.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nmmc: davinci: avoid NULL deref of host-\u003edata in IRQ handler\n\nmmc_davinci_irq() returns early only when both host-\u003ecmd and\nhost-\u003edata are NULL:\n\n  if (host-\u003ecmd == NULL \u0026\u0026 host-\u003edata == NULL) {\n          ...\n          return IRQ_NONE;\n  }\n\nSo we may legitimately reach the rest of the handler with\nhost-\u003edata == NULL (and therefore data == NULL). The DATDNE branch\nalready guards against this with an explicit \"if (data != NULL)\"\ncheck, but the subsequent TOUTRD (\"read data timeout\") and\nCRCWR/CRCRD (\"data CRC error\") branches dereference data\nunconditionally:\n\n  if (qstatus \u0026 MMCST0_TOUTRD) {\n          data-\u003eerror = -ETIMEDOUT;        \u003c-- NULL deref\n          ...\n          davinci_abort_data(host, data);\n  }\n\n  if (qstatus \u0026 (MMCST0_CRCWR | MMCST0_CRCRD)) {\n          data-\u003eerror = -EILSEQ;           \u003c-- NULL deref\n          ...\n  }\n\nIf either bit is set in qstatus while host-\u003edata is NULL, the kernel\nwill crash inside the IRQ handler. smatch flags this:\n\n  drivers/mmc/host/davinci_mmc.c:933 mmc_davinci_irq() error: we\n    previously assumed 'data' could be null (see line 914)\n\nGate both branches on a non-NULL data, matching the existing pattern\nused by the DATDNE branch.\n\nNo functional change for callers where data is non-NULL, which is\nthe only case in which these branches did meaningful work before\nthis change.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"mmc: davinci: avoid NULL deref of host-\u003edata in IRQ handler","id":"CVE-2026-97502","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"genirq/proc: Size interrupt directory names for 10-digit interrupt numbers","id":"CVE-2026-97503"},"packages":[],"prev":{"headline":"pinctrl: mediatek: paris: bypass pinctrl GPIO layer in set GPIO direction","id":"CVE-2026-97501"},"products":["Linux"],"published":"2026-09-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-03","vendors":["Linux"]},"summary":"A NULL pointer dereference in the Linux kernel's Davinci MMC driver IRQ handler allows local attackers to cause a system crash.","url":"https://insights.sbomify.com/CVE-2026-97502/"}