CVE-2022-48750: hwmon: (nct6775) Fix crash in clear_caseopen
In the Linux kernel, the following vulnerability has been resolved:
hwmon: (nct6775) Fix crash in clear_caseopen
Paweł Marciniak reports the following crash, observed when clearing
the chassis intrusion alarm.
BUG: kernel NULL pointer dereference, address: 0000000000000028
PGD 0 P4D 0
Oops: 0000 [#1] PREEMPT SMP PTI
CPU: 3 PID: 4815 Comm: bash Tainted: G S 5.16.2-200.fc35.x86_64 #1
Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z97 Extreme4, BIOS P2.60A 05/03/2018
RIP: 0010:clear_caseopen+0x5a/0x120 [nct6775]
Code: 68 70 e8 e9 32 b1 e3 85 c0 0f 85 d2 00 00 00 48 83 7c 24 ...
RSP: 0018:ffffabcb02803dd8 EFLAGS: 00010246
RAX: 0000000000000000 RBX: 0000000000000002 RCX: 0000000000000000
RDX: ffff8e8808192880 RSI: 0000000000000000 RDI: ffff8e87c7509a68
RBP: 0000000000000000 R08: 0000000000000001 R09: 000000000000000a
R10: 000000000000000a R11: f000000000000000 R12: 000000000000001f
R13: ffff8e87c7509828 R14: ffff8e87c7509a68 R15: ffff8e88494527a0
FS: 00007f4db9151740(0000) GS:ffff8e8ebfec0000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000028 CR3: 0000000166b66001 CR4: 00000000001706e0
Call Trace:
<TASK>
kernfs_fop_write_iter+0x11c/0x1b0
new_sync_write+0x10b/0x180
vfs_write+0x209/0x2a0
ksys_write+0x4f/0xc0
do_syscall_64+0x3b/0x90
entry_SYSCALL_64_after_hwframe+0x44/0xae
The problem is that the device passed to clear_caseopen() is the hwmon
device, not the platform device, and the platform data is not set in the
hwmon device. Store the pointer to sio_data in struct nct6775_data and
get if from there if needed.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can crash a system path used by the nct6775 hardware monitoring driver when clearing a chassis intrusion alarm. It is not described as remote code execution, and the provided sources do not show active exploitation. Exposure appears limited to Linux systems using this driver and affected kernel versions.
Executive priority
Treat this as a targeted stability issue, not an emergency internet-facing compromise. Patch during normal kernel maintenance, with higher priority for systems where hardware monitoring workflows are operationally important.
Technical view
The crash is a NULL pointer dereference in clear_caseopen() in the hwmon nct6775 driver. The function received the hwmon device rather than the platform device, so expected platform data was missing. The fix stores the sio_data pointer in struct nct6775_data and retrieves it from there when needed.
Likely exposure
Likely exposed systems are Linux hosts running affected 5.16-era kernels with nct6775-supported hardware monitoring enabled. The source bundle identifies Linux as affected and references stable kernel fixes, but does not provide distribution-specific package status or a complete hardware inventory condition.
Exploitation context
No provided source reports exploitation, and the KEV flag is false. The reported crash occurred while clearing the chassis intrusion alarm through the kernel hwmon path. The bundle supports local crash risk, not remote compromise or privilege escalation.
Researcher notes
The evidence is concise: a kernel crash report, root cause, and stable commit references. CVSS and CWE data are absent, and distribution impact is not included. Avoid assuming broader exploitability beyond the documented NULL dereference crash path.
Mitigation direction
Apply vendor or distribution kernel updates containing the referenced nct6775 fixes.
Prioritize systems using affected 5.16-era kernels and nct6775 hardware monitoring.
Check Linux vendor advisories for exact fixed package versions.
Restrict operational access to chassis-intrusion clearing workflows to trusted administrators.
Validation and detection
Inventory kernel versions and identify systems in the affected 5.16-era range.
Confirm whether the nct6775 driver is present or loaded on candidate systems.
Verify vendor kernel changelogs include the referenced nct6775 clear_caseopen fix.
Review monitoring or crash logs for kernel oops events mentioning clear_caseopen or nct6775.
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-2022-48750 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.