{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-97978 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-97978 is a vulnerability in Linux, published on 25 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-97978 and fix it if it is affected.\n\nWhat it is: CVE-2026-97978 is a vulnerability in Linux, published on 25 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-97978 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-97978/ (Markdown: https://insights.sbomify.com/CVE-2026-97978/index.md)","id":"CVE-2026-97978","markdown":"https://insights.sbomify.com/CVE-2026-97978/index.md","name":"CVE-2026-97978","record":{"aliases":["AZL-104172","BELL-CVE-2026-97978","DEBIAN-CVE-2026-97978","GHSA-3wqj-8258-77x5","UBUNTU-CVE-2026-97978"],"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 ice driver tracing code can cause a system crash when trace events are processed.","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\neth: ice: don't dereference pointers from TP_printk()\n\nAfter forwarding net-next during the v7.3 merge window we started\nseeing:\n\n  TRACE EVENT ERROR: Event ice_tx_dim_work has double dereference in TP_printk: REC-\u003eq_vector-\u003etx.tx_ring-\u003eq_index\n  WARNING: kernel/trace/trace_events.c:420 at test_double_dereference.cold+0x39/0x4b\n\nthis is due to extra checks added in tracing subsystem in\ncommit b5cc230af5e5 (\"tracing: Warn when an event dereferences a pointer in TP_printk()\").\n\nPrinting happens long after the event was recorded, by which point\nthe pointers may be invalid (the ring or the dim instance).\nCopy the eight scalars into the event instead.","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":"eth: ice: don't dereference pointers from TP_printk()","id":"CVE-2026-97978","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"ice: add missing xa_destroy for sched_node_ids","id":"CVE-2026-97979"},"packages":[],"prev":{"headline":"Bluetooth: btusb: Fix UAF of btusb_data by rx_work","id":"CVE-2026-97977"},"products":["Linux"],"published":"2026-09-25","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-21","vendors":["Linux"]},"summary":"A null pointer dereference in the Linux kernel ice driver tracing code can cause a system crash when trace events are processed.","url":"https://insights.sbomify.com/CVE-2026-97978/"}