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/da90f64c-260a-4329-87bf-1f9ff20a5951@gmail.com/
Security readout for executives and security teams
Plain-English summary
A timing flaw in Linux’s MediaTek T7xx WWAN driver can cause a kernel crash when a modem state-change task finishes after its caller has timed out. Affected systems may lose availability and require recovery. Risk is concentrated on Linux devices that actually use this WWAN driver and relevant hardware.
Executive priority
Treat as a high-priority reliability and kernel-security update where T7xx WWAN is deployed. Establish hardware and driver exposure first, then patch through supported vendor channels. Systems lacking the relevant driver can be deprioritized after verification. There is no supplied evidence of active exploitation.
Technical view
The driver handles internal state changes asynchronously. After a timeout, the main thread can release its completion object while the worker still references it. A later completion notification accesses released memory, producing a page fault and kernel panic. The fix uses reference counting to keep the object alive safely.
Likely exposure
Exposure requires an affected Linux kernel plus the MediaTek T7xx WWAN driver in a relevant operational path. The bundle lists affected release markers, but their precise range semantics are incomplete. Systems without this driver or hardware are unlikely to reach the vulnerable code.
Exploitation context
The CVSS vector describes a local, low-complexity, low-privilege condition requiring no user interaction. However, the supplied sources do not establish a reliable attacker-controlled trigger. The CVE is not listed as KEV, and no cited evidence confirms active exploitation or a public exploit.
Researcher notes
The failure resembles a lifetime-management race involving a completion object rather than a documented direct privilege-escalation primitive. The observed result is a page fault in complete_all from fsm_main_thread. Reference counting addresses the late worker notification. Exact affected and fixed version boundaries should be confirmed through distribution advisories and stable commits.
Mitigation direction
Update to a vendor-supported kernel confirmed to incorporate the referenced stable fix.
Check the Linux distribution or device vendor advisory for the exact fixed package version.
Prioritize WWAN gateways, laptops, and embedded devices confirmed to use the T7xx driver.
Where updating is delayed, ask the vendor for supported risk-reduction guidance.
Validation and detection
Inventory kernel versions on systems using MediaTek T7xx WWAN hardware.
Confirm whether the mtk_t7xx driver is present and actively used.
Verify the installed vendor kernel includes the applicable referenced stable commit.
Review kernel logs for related page faults, oops reports, or panics.
Retest modem state transitions and timeout handling after updating.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-39282 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
6Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.