CVE-2022-49624
net: atlantic: remove aq_nic_deinit() when resume
In the Linux kernel, the following vulnerability has been resolved: net: atlantic: remove aq_nic_deinit() when resume aq_nic_deinit() has been called while suspending, so we don't have to call it again on resume. Actually, call it again leads to another hang issue when resuming from S3. Jul 8 03:09:44 u-Precision-7865-Tower kernel: [ 5910.992345] Call Trace: Jul 8 03:09:44 u-Precision-7865-Tower kernel: [ 5910.992346] <TASK> Jul 8 03:09:44 u-Precision-7865-Tower kernel: [ 5910.992348] aq_nic_deinit+0xb4/0xd0 [atlantic] Jul 8 03:09:44 u-Precision-7865-Tower kernel: [ 5910.992356] aq_pm_thaw+0x7f/0x100 [atlantic] Jul 8 03:09:44 u-Precision-7865-Tower kernel: [ 5910.992362] pci_pm_resume+0x5c/0x90 Jul 8 03:09:44 u-Precision-7865-Tower kernel: [ 5910.992366] ? pci_pm_thaw+0x80/0x80 Jul 8 03:09:44 u-Precision-7865-Tower kernel: [ 5910.992368] dpm_run_callback+0x4e/0x120 Jul 8 03:09:44 u-Precision-7865-Tower kernel: [ 5910.992371] device_resume+0xad/0x200 Jul 8 03:09:44 u-Precision-7865-Tower kernel: [ 5910.992373] async_resume+0x1e/0x40 Jul 8 03:09:44 u-Precision-7865-Tower kernel: [ 5910.992374] async_run_entry_fn+0x33/0x120 Jul 8 03:09:44 u-Precision-7865-Tower kernel: [ 5910.992377] process_one_work+0x220/0x3c0 Jul 8 03:09:44 u-Precision-7865-Tower kernel: [ 5910.992380] worker_thread+0x4d/0x3f0 Jul 8 03:09:44 u-Precision-7865-Tower kernel: [ 5910.992382] ? process_one_work+0x3c0/0x3c0 Jul 8 03:09:44 u-Precision-7865-Tower kernel: [ 5910.992384] kthread+0x12a/0x150 Jul 8 03:09:44 u-Precision-7865-Tower kernel: [ 5910.992386] ? set_kthread_struct+0x40/0x40 Jul 8 03:09:44 u-Precision-7865-Tower kernel: [ 5910.992387] ret_from_fork+0x22/0x30 Jul 8 03:09:44 u-Precision-7865-Tower kernel: [ 5910.992391] </TASK> Jul 8 03:09:44 u-Precision-7865-Tower kernel: [ 5910.992392] ---[ end trace 1ec8c79604ed5e0d ]--- Jul 8 03:09:44 u-Precision-7865-Tower kernel: [ 5910.992394] PM: dpm_run_callback(): pci_pm_resume+0x0/0x90 returns -110 Jul 8 03:09:44 u-Precision-7865-Tower kernel: [ 5910.992397] atlantic 0000:02:00.0: PM: failed to resume async: error -110
Fixes and workarounds
No remediation reported in collected sources.
Missing remediation information is not evidence that no patch exists.
Affected products and versions
| Product | Versions | Authority |
|---|---|---|
| Linux Linux |
≥ 6aa239d82e35b9e3eb8e8c7750fd5caa377e1e15; < c2978d0124f26e453ed30fda6a37f62d8c7f19cb (affected, git) ≥ 890a5c6d19817a9db5c981174737d1bc9b6fb1a1; < 58c90993933e7a76305519bc70da8c0cd2907c1f (affected, git) ≥ 1809c30b6e5a83a1de1435fe01aaa4de4d626a7c; < 702419db7ded2e3686fbc05040b61d7428d611d5 (affected, git) ≥ 1809c30b6e5a83a1de1435fe01aaa4de4d626a7c; < 2e15c51fefaffaf9f72255eaef4fada05055e4c5 (affected, git) fb45f24264b94e8c37657789dbb1966a07933d12 (affected, git) ≥ 5.10.117; < 5.10.132 (affected, semver) ≥ 5.15.41; < 5.15.56 (affected, semver) ≥ 5.17.9; < 5.18 (affected, semver) Other versions: unaffected |
CNA: Linux |
| Linux Linux |
5.18 (affected) ≥ 0; < 5.18 (unaffected, semver) ≥ 5.10.132; ≤ 5.10.* (unaffected, semver) ≥ 5.15.56; ≤ 5.15.* (unaffected, semver) ≥ 5.18.13; ≤ 5.18.* (unaffected, semver) ≥ 5.19; ≤ * (unaffected, original_commit_for_fix) Other versions: affected |
CNA: Linux |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
No CVSS assessment reported. An unscored record is not a low-severity determination.
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://git.kernel.org/stable/c/c2978d0124f26e453ed30fda6a37f62d8c7f19cbCNA: Linux
- https://git.kernel.org/stable/c/58c90993933e7a76305519bc70da8c0cd2907c1fCNA: Linux
- https://git.kernel.org/stable/c/702419db7ded2e3686fbc05040b61d7428d611d5CNA: Linux
- https://git.kernel.org/stable/c/2e15c51fefaffaf9f72255eaef4fada05055e4c5CNA: Linux
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.