Answer in brief
CVE-2024-39282 records a Unknown severity vulnerability in net: wwan: t7xx: Fix FSM command timeout issue. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=13e920d93e37fcaef4a9309515798a3cae9dcf19 <b8ab9bd0c8855cd5a6f4e0265083576257ff3fc5 || >=13e920d93e37fcaef4a9309515798a3cae9dcf19 <0cd3bde081cd3452c875fa1e5c55834c670d6e05 || >=13e920d93e37fcaef4a9309515798a3cae9dcf19 <e6e6882a1590cbdaca77a31a02f4954327237e14 || >=13e920d93e37fcaef4a9309515798a3cae9dcf19 <4f619d518db9cd1a933c3a095a5f95d0c1584ae8 | b8ab9bd0c8855cd5a6f4e0265083576257ff3fc5, 0cd3bde081cd3452c875fa1e5c55834c670d6e05, e6e6882a1590cbdaca77a31a02f4954327237e14, 4f619d518db9cd1a933c3a095a5f95d0c1584ae8 |
| Linux/Linuxgeneric | 5.19 | Not reported |
Published upstream
Jan 15, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: net: wwan: t7xx: Fix FSM command timeout issue When driver processes the internal state change command, it use an asynchronous thread to process the command operation. If the main thread detects that the task has timed out, the asynchronous thread will panic when executing the completion notification because the main thread completion object has been released. BUG: unable to handle page fault for address: fffffffffffffff8 PGD 1f283a067 P4D 1f283a067 PUD 1f283c067 PMD 0 Oops: 0000 [#1] PREEMPT SMP NOPTI RIP: 0010:complete_all+0x3e/0xa0 [...] Call Trace: <TASK> ? __die_body+0x68/0xb0 ? page_fault_oops+0x379/0x3e0 ? exc_page_fault+0x69/0xa0 ? asm_exc_page_fault+0x22/0x30 ? complete_all+0x3e/0xa0 fsm_main_thread+0xa3/0x9c0 [mtk_t7xx (HASH:1400 5)] ? __pfx_autoremove_wake_function+0x10/0x10 kthread+0xd8/0x110 ? __pfx_fsm_main_thread+0x10/0x10 [mtk_t7xx (HASH:1400 5)] ? __pfx_kthread+0x10/0x10 ret_from_fork+0x38/0x50 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1b/0x30 </TASK> [...] CR2: fffffffffffffff8 ---[ end trace 0000000000000000 ]--- Use the reference counter to ensure safe release as Sergey suggests: https://lore.kernel.org/all/[email protected]/
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-39282 records a Unknown severity vulnerability in net: wwan: t7xx: Fix FSM command timeout issue. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=13e920d93e37fcaef4a9309515798a3cae9dcf19 <b8ab9bd0c8855cd5a6f4e0265083576257ff3fc5 || >=13e920d93e37fcaef4a9309515798a3cae9dcf19 <0cd3bde081cd3452c875fa1e5c55834c670d6e05 || >=13e920d93e37fcaef4a9309515798a3cae9dcf19 <e6e6882a1590cbdaca77a31a02f4954327237e14 || >=13e920d93e37fcaef4a9309515798a3cae9dcf19 <4f619d518db9cd1a933c3a095a5f95d0c1584ae8 | b8ab9bd0c8855cd5a6f4e0265083576257ff3fc5, 0cd3bde081cd3452c875fa1e5c55834c670d6e05, e6e6882a1590cbdaca77a31a02f4954327237e14, 4f619d518db9cd1a933c3a095a5f95d0c1584ae8 |
| Linux/Linuxgeneric | 5.19 | Not reported |
Published upstream
Jan 15, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: net: wwan: t7xx: Fix FSM command timeout issue When driver processes the internal state change command, it use an asynchronous thread to process the command operation. If the main thread detects that the task has timed out, the asynchronous thread will panic when executing the completion notification because the main thread completion object has been released. BUG: unable to handle page fault for address: fffffffffffffff8 PGD 1f283a067 P4D 1f283a067 PUD 1f283c067 PMD 0 Oops: 0000 [#1] PREEMPT SMP NOPTI RIP: 0010:complete_all+0x3e/0xa0 [...] Call Trace: <TASK> ? __die_body+0x68/0xb0 ? page_fault_oops+0x379/0x3e0 ? exc_page_fault+0x69/0xa0 ? asm_exc_page_fault+0x22/0x30 ? complete_all+0x3e/0xa0 fsm_main_thread+0xa3/0x9c0 [mtk_t7xx (HASH:1400 5)] ? __pfx_autoremove_wake_function+0x10/0x10 kthread+0xd8/0x110 ? __pfx_fsm_main_thread+0x10/0x10 [mtk_t7xx (HASH:1400 5)] ? __pfx_kthread+0x10/0x10 ret_from_fork+0x38/0x50 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1b/0x30 </TASK> [...] CR2: fffffffffffffff8 ---[ end trace 0000000000000000 ]--- Use the reference counter to ensure safe release as Sergey suggests: https://lore.kernel.org/all/[email protected]/
Quoted source text, attributed separately from HOL analysis.