eth: ice: don't dereference pointers from TP_printk()
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.6.160, 6.12.111, 6.18.53, 7.2.7
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In 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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 3089cf6d3caa1eb344aac05c875f4aeaf891552d · fixed in 385aa7dbc6af11d90a5dd1261dbe75950eb7ca93; From 3089cf6d3caa1eb344aac05c875f4aeaf891552d · fixed in ae230874e3ba27e975a9bb21a6ffd05d6a2ea318; From 3089cf6d3caa1eb344aac05c875f4aeaf891552d · fixed in 0b0d2f9db2406aa541a8bc3737f4f4aae1cafde9; From 3089cf6d3caa1eb344aac05c875f4aeaf891552d · fixed in c42db35518bb0eae42ec955520eee0aa94a4a6fe; From 3089cf6d3caa1eb344aac05c875f4aeaf891552d · fixed in b8bf9bfda5f62e11444e483c2b4aaff90c5cfc6b
- Linux Linux
5.14
- KernelLinux
From 5.14.0 · fixed in 6.6.160; From 6.7.0 · fixed in 6.12.111; From 6.13.0 · fixed in 6.18.53; From 6.19.0 · fixed in 7.2.7