{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2026-64162","assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","state":"PUBLISHED","assignerShortName":"Linux","dateReserved":"2026-07-19T07:54:57.038Z","datePublished":"2026-07-19T15:40:48.461Z","dateUpdated":"2026-08-05T12:39:51.253Z"},"containers":{"cna":{"providerMetadata":{"orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux","dateUpdated":"2026-08-05T12:39:51.253Z"},"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nidpf: fix read_dev_clk_lock spinlock init in idpf_ptp_init()\n\nIn idpf_ptp_init(), read_dev_clk_lock is initialized after\nptp_schedule_worker() had already been called (and after\nidpf_ptp_settime64() could reach the lock). The PTP aux worker\nfires immediately upon scheduling and can call into\nidpf_ptp_read_src_clk_reg_direct(), which takes\nspin_lock(&ptp->read_dev_clk_lock) on an uninitialized lock, triggering\nthe lockdep \"non-static key\" warning:\n\n[12973.796587] idpf 0000:83:00.0: Device HW Reset initiated\n[12974.094507] INFO: trying to register non-static key.\n...\n[12974.097208] Call Trace:\n[12974.097213]  <TASK>\n[12974.097218]  dump_stack_lvl+0x93/0xe0\n[12974.097234]  register_lock_class+0x4c4/0x4e0\n[12974.097249]  ? __lock_acquire+0x427/0x2290\n[12974.097259]  __lock_acquire+0x98/0x2290\n[12974.097272]  lock_acquire+0xc6/0x310\n[12974.097281]  ? idpf_ptp_read_src_clk_reg+0xb7/0x150 [idpf]\n[12974.097311]  ? lockdep_hardirqs_on_prepare+0xde/0x190\n[12974.097318]  ? finish_task_switch.isra.0+0xd2/0x350\n[12974.097330]  ? __pfx_ptp_aux_kworker+0x10/0x10 [ptp]\n[12974.097343]  _raw_spin_lock+0x30/0x40\n[12974.097353]  ? idpf_ptp_read_src_clk_reg+0xb7/0x150 [idpf]\n[12974.097373]  idpf_ptp_read_src_clk_reg+0xb7/0x150 [idpf]\n[12974.097391]  ? kthread_worker_fn+0x88/0x3d0\n[12974.097404]  ? kthread_worker_fn+0x4e/0x3d0\n[12974.097411]  idpf_ptp_update_cached_phctime+0x26/0x120 [idpf]\n[12974.097428]  ? _raw_spin_unlock_irq+0x28/0x50\n[12974.097436]  idpf_ptp_do_aux_work+0x15/0x20 [idpf]\n[12974.097454]  ptp_aux_kworker+0x20/0x40 [ptp]\n[12974.097464]  kthread_worker_fn+0xd5/0x3d0\n[12974.097474]  ? __pfx_kthread_worker_fn+0x10/0x10\n[12974.097482]  kthread+0xf4/0x130\n[12974.097489]  ? __pfx_kthread+0x10/0x10\n[12974.097498]  ret_from_fork+0x32c/0x410\n[12974.097512]  ? __pfx_kthread+0x10/0x10\n[12974.097519]  ret_from_fork_asm+0x1a/0x30\n[12974.097540]  </TASK>\n\nMove the call to spin_lock_init() up a bit to make sure read_dev_clk_lock\nis not touched before it's been initialized."}],"metrics":[{"cvssV3_1":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","baseScore":9.8,"baseSeverity":"CRITICAL"},"scenarios":[{"lang":"en","value":"AV:N - On internet-facing cloud or datacenter hosts using Intel idpf NICs, a remote peer can send sustained or crafted traffic that stalls TX completion, triggering `idpf_tx_timeout()` → hardware reset → `idpf_vc_core_init()` → `idpf_ptp_init()`, which reaches the uninitialized `read_dev_clk_lock` via the immediately scheduled PTP aux worker or `idpf_ptp_settime64()`.\nAC:L - Once PTP reinitialization runs with device clock access enabled, `ptp_schedule_worker(..., 0)` fires the aux kworker immediately and races deterministically with the late `spin_lock_init()`; the attacker does not need to win a timing lottery beyond causing the reset that enters this path.\nPR:N - Triggering the vulnerable init path via TX-timeout-driven hardware reset requires no target-system privileges—only the ability to send traffic to a network interface managed by idpf, including unauthenticated remote access to a publicly reachable server.\nUI:N - Exploitation is fully automated once the attacker induces the reset/recovery sequence; no victim login, configuration change, or other voluntary action is required.\nS:U - Impact is confined to kernel/driver state on the host running idpf; it does not cross a VM, container, or IOMMU security boundary into another authority.\nC:H - Using `spin_lock()` on an uninitialized (zeroed) lock allows concurrent, unsynchronized entry into `idpf_ptp_read_src_clk_reg_direct()` and shared PHC/MMIO read paths, creating a race on kernel/driver state that can be leveraged for information disclosure under the kernel CNA guidance for synchronization-breaking bugs.\nI:H - Concurrent unsynchronized callers can interleave `idpf_ptp_enable_shtime()` MMIO writes and cached PHC updates, corrupting device clock and driver timing state in ways that constitute exploitable integrity impact beyond a benign crash.\nA:H - Taking an uninitialized spinlock during HW-reset recovery can cause kernel deadlock, oops, or hang (lockdep “non-static key” failure was observed in the fix commit’s HW-reset trace), satisfying high availability impact for kernel stability bugs."}]}],"affected":[{"product":"Linux","vendor":"Linux","defaultStatus":"unaffected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/net/ethernet/intel/idpf/idpf_ptp.c"],"versions":[{"version":"5cb8805d2366b20ee4d7afff586d8acf17649330","lessThan":"eb5991d4c8ba2e8153dfcda3e66a9608377b7dce","status":"affected","versionType":"git"},{"version":"5cb8805d2366b20ee4d7afff586d8acf17649330","lessThan":"3122d70b7c0101d897fb795658a7b93f854935f2","status":"affected","versionType":"git"},{"version":"5cb8805d2366b20ee4d7afff586d8acf17649330","lessThan":"da4f76b6a84ede14a71282ef841768299ead0221","status":"affected","versionType":"git"}]},{"product":"Linux","vendor":"Linux","defaultStatus":"affected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/net/ethernet/intel/idpf/idpf_ptp.c"],"versions":[{"version":"6.16","status":"affected"},{"version":"0","lessThan":"6.16","status":"unaffected","versionType":"semver"},{"version":"6.18.34","lessThanOrEqual":"6.18.*","status":"unaffected","versionType":"semver"},{"version":"7.0.11","lessThanOrEqual":"7.0.*","status":"unaffected","versionType":"semver"},{"version":"7.1","lessThanOrEqual":"*","status":"unaffected","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.16","versionEndExcluding":"6.18.34"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.16","versionEndExcluding":"7.0.11"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.16","versionEndExcluding":"7.1"}]}]}],"references":[{"url":"https://git.kernel.org/stable/c/eb5991d4c8ba2e8153dfcda3e66a9608377b7dce"},{"url":"https://git.kernel.org/stable/c/3122d70b7c0101d897fb795658a7b93f854935f2"},{"url":"https://git.kernel.org/stable/c/da4f76b6a84ede14a71282ef841768299ead0221"}],"title":"idpf: fix read_dev_clk_lock spinlock init in idpf_ptp_init()","x_generator":{"engine":"bippy-1.2.0"}}}}