CVE-2024-46842: scsi: lpfc: Handle mailbox timeouts in lpfc_get_sfp_info

Published Sep 27, 2024
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

scsi: lpfc: Handle mailbox timeouts in lpfcgetsfpinfo

The MBXTIMEOUT return code is not handled in lpfcgetsfpinfo and the routine unconditionally frees submitted mailbox commands regardless of return status. The issue is that for MBXTIMEOUT cases, when firmware returns SFP information at a later time, that same mailbox memory region references previously freed memory in its cmpl routine.

Fix by adding checks for the MBXTIMEOUT return code. During mailbox resource cleanup, check the mbox flag to make sure that the wait did not timeout. If the MBOXWAKE flag is not set, then do not free the resources because it will be freed when firmware completes the mailbox at a later time in its cmpl routine.

Also, increase the timeout from 30 to 60 seconds to accommodate boot scripts requiring longer timeouts.

Other sources

This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.

Launchpad

Affected Software

2 affected componentsFixes available
Linux Linux kernel<6.10.10
debian/linux<=5.10.223-1, <=5.10.234-1, <=6.1.129-1, <=6.1.133-1
6.12.22-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.12.22-1
  2. Configuration

    Increase the timeout from 30 to 60 seconds to accommodate boot and boot scripts requiring longer timeouts.

    Boot/initialization scripts (timeout setting) timeout = 60 seconds
  3. Configuration

    Fix lpfc_get_sfp_info to handle the MBX_TIMEOUT return code by adding checks for the MBX_TIMEOUT return code (i.e., do not proceed as if the mailbox returned successfully when MBX_TIMEOUT occurs).

    lpfc_get_sfp_info MBX_TIMEOUT handling = Add checks for MBX_TIMEOUT return code
  4. Configuration

    In lpfc_get_sfp_info, if the MBOX_WAKE flag is not set, do not free the submitted mailbox resources because it will be freed when firmware completes the mailbox at a later time in its cmpl routine.

    lpfc_get_sfp_info MBOX_WAKE behavior = If MBOX_WAKE not set, do not free resources
  5. Configuration

    During mailbox resource cleanup, check the mbox flag to make sure that the wait did not timeout before performing cleanup.

    Mailbox resource cleanup logic mbox flag validation = Check mbox flag to ensure wait did not timeout

Event History

Sep 27, 2024
CVE Published
via MITRE·12:39 PM
Data Sourced
via MITRE·12:39 PM
DescriptionSeverity
Data Sourced
via NVD·01:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Dec 12, 2024
Data Sourced
via Launchpad·06:26 PM
Description
Apr 11, 2025
Data Sourced
via Ubuntu·08:52 PM
RemedyDescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2024-46842?

The severity of CVE-2024-46842 is classified as moderate.

2

How do I fix CVE-2024-46842?

To fix CVE-2024-46842, update your Linux kernel to version 6.12.11-1 or later.

3

Which software is affected by CVE-2024-46842?

CVE-2024-46842 affects Linux kernel versions prior to 6.10.10 and certain Debian packages.

4

What type of vulnerability is CVE-2024-46842?

CVE-2024-46842 is a mailbox timeout handling vulnerability in the SCSI lpfc driver.

5

Is CVE-2024-46842 exploitable remotely?

CVE-2024-46842 is not considered to be remotely exploitable.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203