CVE-2022-49229 | ptp: unregister virtual clocks when unregistering physical clock.

In the Linux kernel, the following vulnerability has been resolved: ptp: unregister virtual clocks when unregistering physical clock. When unregistering a physical clock which has some virtual clocks, unregister the virtual clocks with it. This fixes the following oops, which can be triggered by unloading a driver providing a PTP clock when it has enabled virtual clocks: BUG: unable to handle page fault for address: ffffffffc04fc4d8 Oops: 0000 [#1] PREEMPT SMP NOPTI RIP: 0010:ptp_vclock_read+0x31/0xb0 Call Trace: timecounter_read+0xf/0x50 ptp_vclock_refresh+0x2c/0x50 ? ptp_clock_release+0x40/0x40 ptp_aux_kworker+0x17/0x30 kthread_worker_fn+0x9b/0x240 ? kthread_should_park+0x30/0x30 kthread+0xe2/0x110 ? kthread_complete_and_exit+0x20/0x20 ret_from_fork+0x22/0x30

Published: 2025-02-26 Last update: 2025-10-21 Assigner: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-49229 is rated Low Risk (34.2/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.14%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2022-49229

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-04-06 0.03% 0.14% +0.11%
2 2025-11-21 0.06% 0.03% -0.03%
3 2025-11-18 — 0.06% —

Full EPSS history (6 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-49229

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.5 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 3.6 [email protected]

Weakness enumeration for CVE-2022-49229

OS Trackers for CVE-2022-49229

vendor priority summary link
debian unimportant CVE-2022-49229 unimportant priority: Debian including 1 source packages (linux), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2022-49229
redhat medium — https://access.redhat.com/security/cve/CVE-2022-49229
suse medium CVE-2022-49229 severity moderate: SUSE including 26 source package names (cluster-md-kmp-default, dlm-kmp-default, …), 151 product×package rows across 30 product lines (SLES-LTSS-TERADATA 15 SP2, SUSE Linux Enterprise High Availability Extension 12 SP5, … (30 product lines)): Known Not Affected 151. https://www.suse.com/security/cve/CVE-2022-49229/
ubuntu medium CVE-2022-49229 medium priority: Ubuntu including 130 source packages (linux, linux-allwinner-5.19, …), 1040 status rows across 8 suites (bionic, focal, jammy, noble, oracular, trusty, upstream, xenial): DNE 713, ignored 146, not-affected 101, released 80. https://ubuntu.com/security/CVE-2022-49229

Affected software / configurations for CVE-2022-49229

Vendor Product Version Raw CPE
linux linux_kernel >= 5.14.1, < 5.15.33 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 5.16, < 5.16.19 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 5.17, < 5.17.2 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel 5.14 cpe:2.3:o:linux:linux_kernel:5.14:-:*:*:*:*:*:*
linux linux_kernel 5.14 cpe:2.3:o:linux:linux_kernel:5.14:rc2:*:*:*:*:*:*
linux linux_kernel 5.14 cpe:2.3:o:linux:linux_kernel:5.14:rc3:*:*:*:*:*:*
linux linux_kernel 5.14 cpe:2.3:o:linux:linux_kernel:5.14:rc4:*:*:*:*:*:*
linux linux_kernel 5.14 cpe:2.3:o:linux:linux_kernel:5.14:rc5:*:*:*:*:*:*
linux linux_kernel 5.14 cpe:2.3:o:linux:linux_kernel:5.14:rc6:*:*:*:*:*:*
linux linux_kernel 5.14 cpe:2.3:o:linux:linux_kernel:5.14:rc7:*:*:*:*:*:*

References for CVE-2022-49229

cvelogic Threat Intelligence