CVE-2022-48845: MIPS: smp: fill in sibling and core maps earlier
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.22% (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 32813321f18d5432cec1b1a6ecc964f9ea26d565, 56eaacb8137ba2071ce48d4e3d91979270e139a7, 7315f8538db009605ffba00370678142ef00ac98.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 32813321f18d5432cec1b1a6ecc964f9ea26d565, 56eaacb8137ba2071ce48d4e3d91979270e139a7, 7315f8538db009605ffba00370678142ef00ac98 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: MIPS: smp: fill in sibling and core maps earlier After enabling CONFIG_SCHED_CORE (landed during 5.14 cycle), 2-core 2-thread-per-core interAptiv (CPS-driven) started emitting the following: [ 0.025698] CPU1 revision is: 0001a120 (MIPS interAptiv (multi)) [ 0.048183] ------------[ cut here ]------------ [ 0.048187] WARNING: CPU: 1 PID: 0 at kernel/sched/core.c:6025 sched_core_cpu_starting+0x198/0x240 [ 0.048220] Modules linked in: [ 0.048233] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.17.0-rc3+ #35 b7b319f24073fd9a3c2aa7ad15fb7993eec0b26f [ 0.048247] Stack : 817f0000 00000004 327804c8 810eb050 00000000 00000004 00000000 c314fdd1 [ 0.048278] 830cbd64 819c0000 81800000 817f0000 83070bf4 00000001 830cbd08 00000000 [ 0.048307] 00000000 00000000 815fcbc4 00000000 00000000 00000000 00000000 00000000 [ 0.048334] 00000000 00000000 00000000 00000000 817f0000 00000000 00000000 817f6f34 [ 0.048361] 817f0000 818a3c00 817f0000 00000004 00000000 00000000 4dc33260 0018c933 [ 0.048389] ... [ 0.048396] Call Trace: [ 0.048399] [<8105a7bc>] show_stack+0x3c/0x140 [ 0.048424] [<8131c2a0>] dump_stack_lvl+0x60/0x80 [ 0.048440] [<8108b5c0>] __warn+0xc0/0xf4 [ 0.048454] [<8108b658>] warn_slowpath_fmt+0x64/0x10c [ 0.048467] [<810bd418>] sched_core_cpu_starting+0x198/0x240 [ 0.048483] [<810c6514>] sched_cpu_starting+0x14/0x80 [ 0.048497] [<8108c0f8>] cpuhp_invoke_callback_range+0x78/0x140 [ 0.048510] [<8108d914>] notify_cpu_starting+0x94/0x140 [ 0.048523] [<8106593c>] start_secondary+0xbc/0x280 [ 0.048539] [ 0.048543] ---[ end trace 0000000000000000 ]--- [ 0.048636] Synchronize counters for CPU 1: done. ...for each but CPU 0/boot. Basic debug printks right before the mentioned line say: [ 0.048170] CPU: 1, smt_mask: So smt_mask, which is sibling mask obviously, is empty when entering the function. This is critical, as sched_core_cpu_starting() calculates core-scheduling parameters only once per CPU start, and it's crucial to have all the parameters filled in at that moment (at least it uses cpu_smt_mask() which in fact is `&cpu_sibling_map[cpu]` on MIPS). A bit of debugging led me to that set_cpu_sibling_map() performing the actual map calculation, was being invocated after notify_cpu_start(), and exactly the latter function starts CPU HP callback round (sched_core_cpu_starting() is basically a CPU HP callback). While the flow is same on ARM64 (maps after the notifier, although before calling set_cpu_online()), x86 started calculating sibling maps earlier than starting the CPU HP callbacks in Linux 4.14 (see [0] for the reference). Neither me nor my brief tests couldn't find any potential caveats in calculating the maps right after performing delay calibration, but the WARN splat is now gone. The very same debug prints now yield exactly what I expected from them: [ 0.048433] CPU: 1, smt_mask: 0-1 [0] https://git.kernel.org/pub/scm/linux/kernel/git/mips/linux.git/commit/?id=76ce7cfe35ef
- Published
- Jul 16, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 13th percentile
- CWE
- —
Report tools
Action score
22
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.
Is your version affected? Check itNoroxi 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 |
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
- e545a6140b698b2494daf0b32107bdcc5e901390 and later · before 7315f8538db009605ffba00370678142ef00ac98affected · git
- e545a6140b698b2494daf0b32107bdcc5e901390 and later · before 32813321f18d5432cec1b1a6ecc964f9ea26d565affected · git
- e545a6140b698b2494daf0b32107bdcc5e901390 and later · before 56eaacb8137ba2071ce48d4e3d91979270e139a7affected · git
- e545a6140b698b2494daf0b32107bdcc5e901390 and later · before c2420bc3333111184cdcb112282d13afe1338dd7affected · git
- e545a6140b698b2494daf0b32107bdcc5e901390 and later · before e8ad9ecc406974deb5e7c070f51cc1d09d21dc4baffected · git
- e545a6140b698b2494daf0b32107bdcc5e901390 and later · before be538b764a46be1d0700fd3b6e82fb76bd17f13aaffected · git
- e545a6140b698b2494daf0b32107bdcc5e901390 and later · before 94647aec80d03d6914aa664b7b8e103cd9d63239affected · git
- e545a6140b698b2494daf0b32107bdcc5e901390 and later · before f2703def339c793674010cc9f01bfe4980231808affected · git
- before 2.6.28not affected · semver
Affected versions · NVD (7)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernelbefore 4.9.308
- linux linux kernel4.10 and later · before 4.14.273
- linux linux kernel4.15 and later · before 4.19.236
- linux linux kernel4.20 and later · before 5.4.186
- linux linux kernel5.5 and later · before 5.10.107
- linux linux kernel5.11 and later · before 5.15.30
- linux linux kernel5.16 and later · before 5.16.16
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 5.16.18-1 | 5.16.18-1 |
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-48842Jul 16, 2024 · ice: Fix race condition during interface enslave18Monitor
- ← EarlierCVE-2022-48844Jul 16, 2024 · Bluetooth: hci_core: Fix leaking sent_cmd skb22Monitor
- Later →CVE-2022-48846Jul 16, 2024 · block: release rq qos structures for queue without disk22Monitor
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 | 32813321f18d5432cec1b1a6ecc964f9ea26d565 | Vendor (CNA) |
| Linux Linux | 56eaacb8137ba2071ce48d4e3d91979270e139a7 | Vendor (CNA) |
| Linux Linux | 7315f8538db009605ffba00370678142ef00ac98 | Vendor (CNA) |
| Linux Linux | 94647aec80d03d6914aa664b7b8e103cd9d63239 | Vendor (CNA) |
| Linux Linux | be538b764a46be1d0700fd3b6e82fb76bd17f13a | Vendor (CNA) |
| Linux Linux | c2420bc3333111184cdcb112282d13afe1338dd7 | Vendor (CNA) |
| Linux Linux | e8ad9ecc406974deb5e7c070f51cc1d09d21dc4b | Vendor (CNA) |
| Linux Linux | f2703def339c793674010cc9f01bfe4980231808 | Vendor (CNA) |
| debian:linux | 5.16.18-1 · Debian:12 | 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.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-0977 · Jul 17, 2024(Linux Kernel Güncellemesi)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
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)
—
CVSS 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 (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/56eaacb8137ba2071ce48d4e3d91979270e139a7
- git.kernel.org/stable/c/7315f8538db009605ffba00370678142ef00ac98
- git.kernel.org/stable/c/94647aec80d03d6914aa664b7b8e103cd9d63239
- git.kernel.org/stable/c/be538b764a46be1d0700fd3b6e82fb76bd17f13a
- git.kernel.org/stable/c/c2420bc3333111184cdcb112282d13afe1338dd7
- git.kernel.org/stable/c/e8ad9ecc406974deb5e7c070f51cc1d09d21dc4b
- git.kernel.org/stable/c/f2703def339c793674010cc9f01bfe4980231808
Vendor advisories and official records. Exploit/PoC links are deliberately left out.