LiveActive security incident?Get immediate response
CVE Record

CVE-2022-48845: MIPS: smp: fill in sibling and core maps earlier

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

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2022-48845 is a Linux kernel MIPS scheduling initialization bug. Some MIPS systems could start secondary CPUs before sibling and core CPU maps were populated, triggering scheduler warnings and potentially incorrect core-scheduling setup. The sources do not describe remote exploitation, privilege escalation, data theft, or service impact.

Executive priority

Treat this as a targeted platform maintenance issue, not an internet-wide emergency based on current evidence. Prioritize organizations operating MIPS-based appliances, embedded systems, or custom kernels, especially where vendor firmware updates lag.

Technical view

On MIPS, set_cpu_sibling_map() ran after notify_cpu_starting(), while sched_core_cpu_starting() needed cpu_sibling_map during CPU hotplug startup. With CONFIG_SCHED_CORE, affected systems could enter the scheduler callback with an empty SMT mask. The fix moves sibling/core map population earlier, after delay calibration and before CPU hotplug callbacks.

Likely exposure

Exposure appears limited to Linux kernel deployments on MIPS, especially SMP/SMT systems using CONFIG_SCHED_CORE. The bundle lists Linux 2.6.28 through 5.17-era affected version ranges and several stable kernel fix commits. Non-MIPS systems are not identified as affected in the supplied sources.

Exploitation context

No active exploitation is identified. The record is not in KEV, has no CVSS score, and the public description centers on boot-time scheduler warnings and incorrect initialization ordering. The supplied evidence does not establish a practical exploit path or attacker prerequisites.

Researcher notes

The useful research question is operational impact, not weaponization. Sources show a scheduler initialization ordering defect and stable backports, but do not document security impact beyond incorrect core-scheduling setup. Validate architecture, config, and patch presence before assigning urgency.

Mitigation direction

  • Check vendor or distribution advisories for kernels containing the referenced stable fixes.
  • Prioritize MIPS SMP/SMT systems running CONFIG_SCHED_CORE or affected kernel ranges.
  • Upgrade to a maintained kernel release that includes the MIPS sibling/core map timing fix.
  • For embedded appliances, request firmware status from the device vendor.

Validation and detection

  • Inventory Linux kernel versions and CPU architecture on exposed systems.
  • Confirm whether deployed kernels include one of the referenced stable commits.
  • Review boot logs for sched_core_cpu_starting warnings on MIPS systems.
  • Check kernel configuration for CONFIG_SCHED_CORE on MIPS builds.
Prepared
Confidence
medium
Sources
10

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-48845 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

0CVSS vectors
3Timeline events
2ADP providers
9Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxe545a6140b698b2494daf0b32107bdcc5e901390, e545a6140b698b2494daf0b32107bdcc5e901390, e545a6140b698b2494daf0b32107bdcc5e901390, e545a6140b698b2494daf0b32107bdcc5e901390, e545a6140b698b2494daf0b32107bdcc5e901390, e545a6140b698b2494daf0b32107bdcc5e901390, e545a6140b698b2494daf0b32107bdcc5e901390, e545a6140b698b2494daf0b32107bdcc5e901390unaffected
LinuxLinux2.6.28, 0, 4.9.308, 4.14.273, 4.19.236, 5.4.186, 5.10.107, 5.15.30, 5.16.16, 5.17affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.