GHSA-3WQJ-8258-77X5
Vulnerability from github – Published: 2026-09-25 12:31 – Updated: 2026-09-25 12:31In the Linux kernel, the following vulnerability has been resolved:
eth: ice: don't dereference pointers from TP_printk()
After forwarding net-next during the v7.3 merge window we started seeing:
TRACE EVENT ERROR: Event ice_tx_dim_work has double dereference in TP_printk: REC->q_vector->tx.tx_ring->q_index WARNING: kernel/trace/trace_events.c:420 at test_double_dereference.cold+0x39/0x4b
this is due to extra checks added in tracing subsystem in commit b5cc230af5e5 ("tracing: Warn when an event dereferences a pointer in TP_printk()").
Printing happens long after the event was recorded, by which point the pointers may be invalid (the ring or the dim instance). Copy the eight scalars into the event instead.
{
"affected": [],
"aliases": [
"CVE-2026-97978"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-25T11:17:25Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\neth: ice: don\u0027t 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.",
"id": "GHSA-3wqj-8258-77x5",
"modified": "2026-09-25T12:31:31Z",
"published": "2026-09-25T12:31:31Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-97978"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/0b0d2f9db2406aa541a8bc3737f4f4aae1cafde9"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/ae230874e3ba27e975a9bb21a6ffd05d6a2ea318"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/b8bf9bfda5f62e11444e483c2b4aaff90c5cfc6b"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/c42db35518bb0eae42ec955520eee0aa94a4a6fe"
}
],
"schema_version": "1.4.0",
"severity": []
}
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.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
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.