Threats Tagged 'cve-2025-40171'
View all threats tagged with 'cve-2025-40171'. Filter and sort to focus on specific types of threats.
Stop chasing alerts. Route them.
Start free, then upgrade once to turn Radar into an automated delivery engine for your security stack.
Custom feeds / Automations: email, Slack, webhooks, SIEM/MISP / API access (baseline limits)
API access activates after upgrading in Console -> Billing.
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.
Filter Threats
Narrow down the results by type, severity, or affected countries
Threats Tagged 'cve-2025-40171'
Click on any threat for detailed analysis and mitigation recommendations
A high-severity vulnerability in the Linux kernel's nvmet-fc component was resolved by moving the lsop put work item to the nvmet_fc_ls_req_op structure. The issue allowed multiple asynchronous commands to be in flight simultaneously, each taking a tgtport reference, but only one put work item was queued at a time, causing a reference leak. This fix ensures proper tracking and release of resources associated with each command. Join the discussion | GCVE Database | 11/12/2025, 12:30:28 UTC Added: 07/30/2026, 15:50:45 UTC |
In the Linux kernel, the following vulnerability has been resolved: nvmet-fc: move lsop put work to nvmet_fc_ls_req_op It’s possible for more than one async command to be in flight from __nvmet_fc_send_ls_req. For each command, a tgtport reference is taken. In the current code, only one put work item is queued at a time, which results in a leaked reference. To fix this, move the work item to the nvmet_fc_ls_req_op struct, which already tracks all resources related to the command. Join the discussion | GCVE Database | 11/12/2025, 11:15:00 UTC Added: 07/18/2026, 11:37:23 UTC |
Showing 1 to 2 of 2 results