LiveActive security incident?Get immediate response
CVE Record

CVE-2022-48745: net/mlx5: Use del_timer_sync in fw reset flow of halting poll

In the Linux kernel, the following vulnerability has been resolved: net/mlx5: Use del_timer_sync in fw reset flow of halting poll Substitute del_timer() with del_timer_sync() in fw reset polling deactivation flow, in order to prevent a race condition which occurs when del_timer() is called and timer is deactivated while another process is handling the timer interrupt. A situation that led to the following call trace: RIP: 0010:run_timer_softirq+0x137/0x420 <IRQ> recalibrate_cpu_khz+0x10/0x10 ktime_get+0x3e/0xa0 ? sched_clock_cpu+0xb/0xc0 __do_softirq+0xf5/0x2ea irq_exit_rcu+0xc1/0xf0 sysvec_apic_timer_interrupt+0x9e/0xc0 asm_sysvec_apic_timer_interrupt+0x12/0x20 </IRQ>

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel flaw in the mlx5 network driver’s firmware reset handling. A timer race can occur when shutdown of polling overlaps with timer interrupt handling, producing a kernel call trace and potential system instability. The sources do not provide a CVSS score or active exploitation evidence.

Executive priority

Handle through normal kernel vulnerability management, with higher priority for production hosts using mlx5 networking. There is no cited active exploitation or severity score, so this is not source-supported as an emergency patch, but kernel stability issues can affect availability-sensitive infrastructure.

Technical view

The fix replaces del_timer() with del_timer_sync() in the mlx5 firmware reset polling deactivation path. The issue is a race where a timer is deactivated while another context is processing its interrupt handler. Public data lists Linux kernel versions and stable commits, but does not provide CWE, CVSS, or exploitability detail.

Likely exposure

Exposure is most relevant to Linux systems running affected kernel builds with the mlx5 driver present and firmware reset handling reachable. Exact exposure depends on distribution backports and whether the referenced stable commits are included in the deployed kernel package.

Exploitation context

The bundle marks KEV as false and provides no source claiming active exploitation. The evidence describes a kernel race and call trace, not a public exploit path or attacker-controlled trigger. Treat exploitation status as unproven.

Researcher notes

Evidence is limited to the CVE description and kernel stable references. The core research task is version mapping: determine which distro kernels include the del_timer_sync change in the mlx5 firmware reset flow. Avoid assuming remote exploitability from the available text.

Mitigation direction

  • Map deployed kernels to vendor advisories and stable commit inclusion.
  • Update affected Linux kernels through the operating system vendor channel.
  • Prioritize systems using mlx5-supported network adapters or drivers.
  • Monitor kernel logs for timer softirq call traces around mlx5 firmware reset.
  • Check vendor guidance if a kernel update is not immediately available.

Validation and detection

  • Inventory Linux kernel versions across servers and appliances.
  • Confirm whether the mlx5 driver is loaded or packaged.
  • Compare kernel build changelogs against the listed stable commits.
  • Review dmesg or centralized logs for matching timer call traces.
  • Verify patched systems are running the updated kernel after reboot.
Prepared
Confidence
medium
Sources
6

Public sources used

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-48745 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
5Source 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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux38b9f903f22b9baa5c4b9bfb07c8bbc49f5efbba, 38b9f903f22b9baa5c4b9bfb07c8bbc49f5efbba, 38b9f903f22b9baa5c4b9bfb07c8bbc49f5efbba, 38b9f903f22b9baa5c4b9bfb07c8bbc49f5efbbaunaffected
LinuxLinux5.10, 0, 5.10.97, 5.15.20, 5.16.6, 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.