CVE-2022-48953: rtc: cmos: Fix event handler registration ordering issue
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.24% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0bcfccb48696aba475f046c2021f0733659ce0ef, 1ba745fce13d19775100eece30b0bfb8b8b10ea6, 4919d3eb2ec0ee364f7e3cf2d99646c1b224fae8.
Low priority for now. Upgrade to Linux Linux 0bcfccb48696aba475f046c2021f0733659ce0ef, 1ba745fce13d19775100eece30b0bfb8b8b10ea6, 4919d3eb2ec0ee364f7e3cf2d99646c1b224fae8 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: rtc: cmos: Fix event handler registration ordering issue Because acpi_install_fixed_event_handler() enables the event automatically on success, it is incorrect to call it before the handler routine passed to it is ready to handle events. Unfortunately, the rtc-cmos driver does exactly the incorrect thing by calling cmos_wake_setup(), which passes rtc_handler() to acpi_install_fixed_event_handler(), before cmos_do_probe(), because rtc_handler() uses dev_get_drvdata() to get to the cmos object pointer and the driver data pointer is only populated in cmos_do_probe(). This leads to a NULL pointer dereference in rtc_handler() on boot if the RTC fixed event happens to be active at the init time. To address this issue, change the initialization ordering of the driver so that cmos_wake_setup() is always called after a successful cmos_do_probe() call. While at it, change cmos_pnp_probe() to call cmos_do_probe() after the initial if () statement used for computing the IRQ argument to be passed to cmos_do_probe() which is cleaner than calling it in each branch of that if () (local variable "irq" can be of type int, because it is passed to that function as an argument of type int). Note that commit 6492fed7d8c9 ("rtc: rtc-cmos: Do not check ACPI_FADT_LOW_POWER_S0") caused this issue to affect a larger number of systems, because previously it only affected systems with ACPI_FADT_LOW_POWER_S0 set, but it is present regardless of that commit.
- Published
- Oct 21, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 15th percentile
- CWE
- CWE-476
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel2.6.28 and later · before 5.10.163
- linux linux kernel5.11 and later · before 5.15.86
- linux linux kernel5.16 and later · before 6.0.14
- linux linux kernel6.1
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.28affected
- a474aaedac99ba86e28ef6c912a7647c482db6dd and later · before 0bcfccb48696aba475f046c2021f0733659ce0efaffected · git
- a474aaedac99ba86e28ef6c912a7647c482db6dd and later · before 60c6e563a843032cf6ff84b2fb732cd8754fc10daffected · git
- a474aaedac99ba86e28ef6c912a7647c482db6dd and later · before 1ba745fce13d19775100eece30b0bfb8b8b10ea6affected · git
- a474aaedac99ba86e28ef6c912a7647c482db6dd and later · before 4919d3eb2ec0ee364f7e3cf2d99646c1b224fae8affected · git
- before 2.6.28not affected · semver
- 5.10.163 and later · up to and including 5.10.*not affected · semver
- 5.15.86 and later · up to and including 5.15.*not affected · semver
- 6.0.14 and later · up to and including 6.0.*not affected · semver
- 6.1 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.4-1 | 6.1.4-1 |
| openSUSE:Leap 15.5 | kernel-azure | before 5.14.21-150500.33.72.1 | 5.14.21-150500.33.72.1 |
| openSUSE:Leap 15.5 | kernel-rt_debug | before 5.14.21-150500.13.76.1 | 5.14.21-150500.13.76.1 |
| openSUSE:Leap 15.5 | kernel-source-azure | before 5.14.21-150500.33.72.1 | 5.14.21-150500.33.72.1 |
| openSUSE:Leap 15.5 | kernel-source-rt | before 5.14.21-150500.13.76.1 | 5.14.21-150500.13.76.1 |
| openSUSE:Leap 15.5 | kernel-syms-azure | before 5.14.21-150500.33.72.1 | 5.14.21-150500.33.72.1 |
| openSUSE:Leap 15.5 | kernel-syms-rt | before 5.14.21-150500.13.76.1 | 5.14.21-150500.13.76.1 |
| openSUSE:Leap Micro 5.5 | kernel-rt | before 5.14.21-150500.13.76.1 | 5.14.21-150500.13.76.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | kernel-64kb | before 5.14.21-150400.24.141.1 | 5.14.21-150400.24.141.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | kernel-docs | before 5.14.21-150400.24.141.1 | 5.14.21-150400.24.141.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | kernel-obs-build | before 5.14.21-150400.24.141.1 | 5.14.21-150400.24.141.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | kernel-source | before 5.14.21-150400.24.141.1 | 5.14.21-150400.24.141.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | kernel-syms | before 5.14.21-150400.24.141.1 | 5.14.21-150400.24.141.1 |
| SUSE:Linux Enterprise Live Patching 12 SP5 | kernel-default | before 4.12.14-122.250.1 | 4.12.14-122.250.1 |
| SUSE:Linux Enterprise Live Patching 12 SP5 | kgraft-patch-SLE12-SP5_Update_66 | before 1-8.3.1 | 1-8.3.1 |
| SUSE:Linux Enterprise Live Patching 15 SP4 | kernel-livepatch-SLE15-SP4_Update_33 | before 1-150400.9.5.1 | 1-150400.9.5.1 |
| SUSE:Linux Enterprise Live Patching 15 SP5 | kernel-livepatch-SLE15-SP5_Update_21 | before 1-150500.11.5.1 | 1-150500.11.5.1 |
| SUSE:Linux Enterprise Live Patching 15 SP5 | kernel-livepatch-SLE15-SP5-RT_Update_22 | before 1-150500.11.3.1 | 1-150500.11.3.1 |
| SUSE:Linux Enterprise Micro 5.3 | kernel-default | before 5.14.21-150400.24.141.1 | 5.14.21-150400.24.141.1 |
| SUSE:Linux Enterprise Micro 5.3 | kernel-default-base | before 5.14.21-150400.24.141.1.150400.24.68.2 | 5.14.21-150400.24.141.1.150400.24.68.2 |
| SUSE:Linux Enterprise Micro 5.3 | kernel-rt | before 5.14.21-150400.15.100.1 | 5.14.21-150400.15.100.1 |
| SUSE:Linux Enterprise Micro 5.3 | kernel-source-rt | before 5.14.21-150400.15.100.1 | 5.14.21-150400.15.100.1 |
| SUSE:Linux Enterprise Micro 5.5 | kernel-default | before 5.14.21-150500.55.88.1 | 5.14.21-150500.55.88.1 |
| SUSE:Linux Enterprise Micro 5.5 | kernel-default-base | before 5.14.21-150500.55.88.1.150500.6.39.4 | 5.14.21-150500.55.88.1.150500.6.39.4 |
+16
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2022-48951Oct 21, 2024 · ASoC: ops: Check bounds for second channel in snd_soc_put_volsw_sx()31Monitor
- ← EarlierCVE-2022-48952Oct 21, 2024 · PCI: mt7621: Add sentinel to quirks table22Monitor
- Later →CVE-2022-48954Oct 21, 2024 · s390/qeth: fix use-after-free in hsci31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0bcfccb48696aba475f046c2021f0733659ce0ef | Vendor (CNA) |
| Linux Linux | 1ba745fce13d19775100eece30b0bfb8b8b10ea6 | Vendor (CNA) |
| Linux Linux | 4919d3eb2ec0ee364f7e3cf2d99646c1b224fae8 | Vendor (CNA) |
| Linux Linux | 60c6e563a843032cf6ff84b2fb732cd8754fc10d | Vendor (CNA) |
| debian:linux | 6.1.4-1 · Debian:12 | Package registry (OSV) |
| opensuse:kernel-azure | 5.14.21-150500.33.72.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-rt | 5.14.21-150500.13.76.1 · openSUSE:Leap Micro 5.5 | Package registry (OSV) |
| opensuse:kernel-rt_debug | 5.14.21-150500.13.76.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-source-azure | 5.14.21-150500.33.72.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-source-rt | 5.14.21-150500.13.76.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-syms-azure | 5.14.21-150500.33.72.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-syms-rt | 5.14.21-150500.13.76.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| suse:kernel-64kb | 5.14.21-150400.24.141.1 · SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | Package registry (OSV) |
| suse:kernel-azure | 5.14.21-150500.33.72.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP5 | Package registry (OSV) |
| suse:kernel-default | 5.14.21-150400.24.141.1 · SUSE:Linux Enterprise Micro 5.3 | Package registry (OSV) |
| suse:kernel-default-base | 5.14.21-150400.24.141.1.150400.24.68.2 · SUSE:Linux Enterprise Micro 5.3 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP4_Update_33 | 1-150400.9.5.1 · SUSE:Linux Enterprise Live Patching 15 SP4 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP5-RT_Update_22 | 1-150500.11.3.1 · SUSE:Linux Enterprise Live Patching 15 SP5 | Package registry (OSV) |
| suse:kernel-rt | 5.14.21-150500.13.76.1 · SUSE:Linux Enterprise Micro 5.5 | Package registry (OSV) |
| suse:kernel-rt_debug | 5.14.21-150500.13.76.1 · SUSE:Real Time Module 15 SP5 | Package registry (OSV) |
| suse:kernel-source-azure | 5.14.21-150500.33.72.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP5 | Package registry (OSV) |
| suse:kernel-source-rt | 5.14.21-150500.13.76.1 · SUSE:Linux Enterprise Micro 5.5 | Package registry (OSV) |
| suse:kernel-syms-azure | 5.14.21-150500.33.72.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP5 | Package registry (OSV) |
| suse:kernel-syms-rt | 5.14.21-150500.13.76.1 · SUSE:Real Time Module 15 SP5 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-476 · NULL Pointer DereferenceCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.