Answer in brief
CVE-2024-42286 records a Unknown severity vulnerability in scsi: qla2xxx: validate nvme_local_port correctly. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2024-42286 records a Unknown severity vulnerability in scsi: qla2xxx: validate nvme_local_port correctly. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=8777e4314d397c4e3615dc02fe8537e571e3922f <549aac9655320c9b245a24271b204668c5d40430 || >=8777e4314d397c4e3615dc02fe8537e571e3922f <e1f010844443c389bc552884ac5cfa47de34d54c || >=8777e4314d397c4e3615dc02fe8537e571e3922f <a3ab508a4853a9f5ae25a7816a4889f09938f63c || >=8777e4314d397c4e3615dc02fe8537e571e3922f <cde43031df533751b4ead37d173922feee2f550f || >=8777e4314d397c4e3615dc02fe8537e571e3922f <7cec2c3bfe84539c415f5e16f989228eba1d2f1e || >=8777e4314d397c4e3615dc02fe8537e571e3922f <f6be298cc1042f24d521197af29c7c4eb95af4d5 || >=8777e4314d397c4e3615dc02fe8537e571e3922f <3eac973eb5cb2b874b3918f924798afc5affd46b || >=8777e4314d397c4e3615dc02fe8537e571e3922f <eb1d4ce2609584eeb7694866f34d4b213caa3af9 | 549aac9655320c9b245a24271b204668c5d40430, e1f010844443c389bc552884ac5cfa47de34d54c, a3ab508a4853a9f5ae25a7816a4889f09938f63c, cde43031df533751b4ead37d173922feee2f550f, 7cec2c3bfe84539c415f5e16f989228eba1d2f1e, f6be298cc1042f24d521197af29c7c4eb95af4d5, 3eac973eb5cb2b874b3918f924798afc5affd46b, eb1d4ce2609584eeb7694866f34d4b213caa3af9 |
| Linux/Linuxgeneric | 4.19 | Not reported |
Published upstream
Aug 17, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: validate nvme_local_port correctly The driver load failed with error message, qla2xxx [0000:04:00.0]-ffff:0: register_localport failed: ret=ffffffef and with a kernel crash, BUG: unable to handle kernel NULL pointer dereference at 0000000000000070 Workqueue: events_unbound qla_register_fcport_fn [qla2xxx] RIP: 0010:nvme_fc_register_remoteport+0x16/0x430 [nvme_fc] RSP: 0018:ffffaaa040eb3d98 EFLAGS: 00010282 RAX: 0000000000000000 RBX: ffff9dfb46b78c00 RCX: 0000000000000000 RDX: ffff9dfb46b78da8 RSI: ffffaaa040eb3e08 RDI: 0000000000000000 RBP: ffff9dfb612a0a58 R08: ffffffffaf1d6270 R09: 3a34303a30303030 R10: 34303a303030305b R11: 2078787832616c71 R12: ffff9dfb46b78dd4 R13: ffff9dfb46b78c24 R14: ffff9dfb41525300 R15: ffff9dfb46b78da8 FS: 0000000000000000(0000) GS:ffff9dfc67c00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000070 CR3: 000000018da10004 CR4: 00000000000206f0 Call Trace: qla_nvme_register_remote+0xeb/0x1f0 [qla2xxx] ? qla2x00_dfs_create_rport+0x231/0x270 [qla2xxx] qla2x00_update_fcport+0x2a1/0x3c0 [qla2xxx] qla_register_fcport_fn+0x54/0xc0 [qla2xxx] Exit the qla_nvme_register_remote() function when qla_nvme_register_hba() fails and correctly validate nvme_local_port.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=8777e4314d397c4e3615dc02fe8537e571e3922f <549aac9655320c9b245a24271b204668c5d40430 || >=8777e4314d397c4e3615dc02fe8537e571e3922f <e1f010844443c389bc552884ac5cfa47de34d54c || >=8777e4314d397c4e3615dc02fe8537e571e3922f <a3ab508a4853a9f5ae25a7816a4889f09938f63c || >=8777e4314d397c4e3615dc02fe8537e571e3922f <cde43031df533751b4ead37d173922feee2f550f || >=8777e4314d397c4e3615dc02fe8537e571e3922f <7cec2c3bfe84539c415f5e16f989228eba1d2f1e || >=8777e4314d397c4e3615dc02fe8537e571e3922f <f6be298cc1042f24d521197af29c7c4eb95af4d5 || >=8777e4314d397c4e3615dc02fe8537e571e3922f <3eac973eb5cb2b874b3918f924798afc5affd46b || >=8777e4314d397c4e3615dc02fe8537e571e3922f <eb1d4ce2609584eeb7694866f34d4b213caa3af9 | 549aac9655320c9b245a24271b204668c5d40430, e1f010844443c389bc552884ac5cfa47de34d54c, a3ab508a4853a9f5ae25a7816a4889f09938f63c, cde43031df533751b4ead37d173922feee2f550f, 7cec2c3bfe84539c415f5e16f989228eba1d2f1e, f6be298cc1042f24d521197af29c7c4eb95af4d5, 3eac973eb5cb2b874b3918f924798afc5affd46b, eb1d4ce2609584eeb7694866f34d4b213caa3af9 |
| Linux/Linuxgeneric | 4.19 | Not reported |
Published upstream
Aug 17, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: validate nvme_local_port correctly The driver load failed with error message, qla2xxx [0000:04:00.0]-ffff:0: register_localport failed: ret=ffffffef and with a kernel crash, BUG: unable to handle kernel NULL pointer dereference at 0000000000000070 Workqueue: events_unbound qla_register_fcport_fn [qla2xxx] RIP: 0010:nvme_fc_register_remoteport+0x16/0x430 [nvme_fc] RSP: 0018:ffffaaa040eb3d98 EFLAGS: 00010282 RAX: 0000000000000000 RBX: ffff9dfb46b78c00 RCX: 0000000000000000 RDX: ffff9dfb46b78da8 RSI: ffffaaa040eb3e08 RDI: 0000000000000000 RBP: ffff9dfb612a0a58 R08: ffffffffaf1d6270 R09: 3a34303a30303030 R10: 34303a303030305b R11: 2078787832616c71 R12: ffff9dfb46b78dd4 R13: ffff9dfb46b78c24 R14: ffff9dfb41525300 R15: ffff9dfb46b78da8 FS: 0000000000000000(0000) GS:ffff9dfc67c00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000070 CR3: 000000018da10004 CR4: 00000000000206f0 Call Trace: qla_nvme_register_remote+0xeb/0x1f0 [qla2xxx] ? qla2x00_dfs_create_rport+0x231/0x270 [qla2xxx] qla2x00_update_fcport+0x2a1/0x3c0 [qla2xxx] qla_register_fcport_fn+0x54/0xc0 [qla2xxx] Exit the qla_nvme_register_remote() function when qla_nvme_register_hba() fails and correctly validate nvme_local_port.
Quoted source text, attributed separately from HOL analysis.