Linux KernelOperating system · Linux

CVE-2022-49156

MEDIUM · 5.5 CVSS v3.1 Published 2025-02-26

Fix available

A fix is available. Upgrade to 5.10.110 / 5.15.33 or later.

See remediation →

57/100

Remediation priority · Elevated

Zero-click Patch available

Official description

NVD · unedited

In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Fix scheduling while atomic The driver makes a call into midlayer (fc_remote_port_delete) which can put the thread to sleep. The thread that originates the call is in interrupt context. The combination of the two trigger a crash. Schedule the call in non-interrupt context where it is more safe. kernel: BUG: scheduling while atomic: swapper/7/0/0x00010000 kernel: Call Trace: kernel: <IRQ> kernel: dump_stack+0x66/0x81 kernel: __schedule_bug.cold.90+0x5/0x1d kernel: __schedule+0x7af/0x960 kernel: schedule+0x28/0x80 kernel: schedule_timeout+0x26d/0x3b0 kernel: wait_for_completion+0xb4/0x140 kernel: ? wake_up_q+0x70/0x70 kernel: __wait_rcu_gp+0x12c/0x160 kernel: ? sdev_evt_alloc+0xc0/0x180 [scsi_mod] kernel: synchronize_sched+0x6c/0x80 kernel: ? call_rcu_bh+0x20/0x20 kernel: ? __bpf_trace_rcu_invoke_callback+0x10/0x10 kernel: sdev_evt_alloc+0xfd/0x180 [scsi_mod] kernel: starget_for_each_device+0x85/0xb0 [scsi_mod] kernel: ? scsi_init_io+0x360/0x3d0 [scsi_mod] kernel: scsi_init_io+0x388/0x3d0 [scsi_mod] kernel: device_for_each_child+0x54/0x90 kernel: fc_remote_port_delete+0x70/0xe0 [scsi_transport_fc] kernel: qla2x00_schedule_rport_del+0x62/0xf0 [qla2xxx] kernel: qla2x00_mark_device_lost+0x9c/0xd0 [qla2xxx] kernel: qla24xx_handle_plogi_done_event+0x55f/0x570 [qla2xxx] kernel: qla2x00_async_login_sp_done+0xd2/0x100 [qla2xxx] kernel: qla24xx_logio_entry+0x13a/0x3c0 [qla2xxx] kernel: qla24xx_process_response_queue+0x306/0x400 [qla2xxx] kernel: qla24xx_msix_rsp_q+0x3f/0xb0 [qla2xxx] kernel: __handle_irq_event_percpu+0x40/0x180 kernel: handle_irq_event_percpu+0x30/0x80 kernel: handle_irq_event+0x36/0x60

Technical summary

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions

NVD · CPE data

Linux KernelOperating system

Affected:< 5.10.110>= 5.11, < 5.15.33>= 5.16, < 5.16.19>= 5.17, < 5.17.2

CVSS breakdown

From the vector

Attack vector: Local
Complexity: Low
Privileges: Low
User interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Remediation

dbcve · scoped

Upgrade available Upgrade to 5.10.110 / 5.15.33 / 5.16.19 or later

Fixed in 5.10.1105.15.335.16.19

Vendor patch git.kernel.org →

Recommended fix High confidence

Upgrade to kernel 5.10.110, 5.15.33, 5.16.19, 5.17.2 or later (choose the latest stable release in your major version branch)

1. Identify the current kernel version using `uname -r`
2. Determine which distribution you are using (e.g., RHEL/CentOS, Ubuntu, Debian, etc.)
3. For RHEL/CentOS: Run `sudo yum update kernel` or `sudo dnf update kernel` to install the latest stable kernel
4. For Ubuntu/Debian: Run `sudo apt-get update && sudo apt-get dist-upgrade` or manually install the specific kernel package
5. For upstream/custom kernels: Download and install kernel 5.10.110 or later, 5.15.33 or later, 5.16.19 or later, or 5.17.2 or later from https://kernel.org/
6. After installation, reboot the system to load the new kernel: `sudo reboot`
7. Verify the fix is applied by running `uname -r` and confirming the version matches a fixed release (e.g., 5.10.110, 5.15.33, 5.16.19, or 5.17.2 or higher)
8. Verify the qla2xxx driver loads without errors: `modprobe qla2xxx` and check `dmesg | grep qla2xxx`

Caveat Kernel upgrades may require updating dependent modules or drivers; ensure compatibility with your system configuration before rebooting

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2022-49156 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-49156 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2022-49156?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here

Verified mitigations, workarounds, and config changes
Version or environment caveats, and links to real fixes
No weaponised exploit code, or anything meant to cause harm
No spam, self-promotion, credentials, or personal data

At a glance

A fix existsUpgrade to 5.10.110 / 5.15.33 or later

Severity 5.5 Medium

Exploit likelihood EPSS, next 30 days 0.3%

Affects: Linux Kernel

Remediation

Need this fixed?

Get a fix

Estimated effortfrom ~9 hrs

ComplexityModerate

Typical engagementfrom $1,600

What a fix involves

We scope it with you and confirm a fixed quote
A specialist builds a reviewed fix
You deploy it to staging first
Optional re-test once it’s live

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2022-49156 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Remediation

References