CVE-2022-48637

Description

In the Linux kernel, the following vulnerability has been resolved: bnxt: prevent skb UAF after handing over to PTP worker When reading the timestamp is required bnxt_tx_int() hands over the ownership of the completed skb to the PTP worker. The skb should not be used afterwards, as the worker may run before the rest of our code and free the skb, leading to a use-after-free. Since dev_kfree_skb_any() accepts NULL make the loss of ownership more obvious and set skb to NULL.

CVSS Metrics

• v3.1•HIGH•Score: 7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS Trends

Current EPSS score: 0.02%• Percentile: 5%

Techniques & Countermeasures

• CWE-416•Use After Free

  The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.

Affected Systems

• linux•linux

  ≥ 83bb623c968e7351aee5111547693f95f330dc5a, < 08483e4c0c83b221b8891434a04cec405dee94a6 | ≥ 83bb623c968e7351aee5111547693f95f330dc5a, < 32afa1f23e42cc635ccf4c39f24514d03d1e8338 | ≥ 83bb623c968e7351aee5111547693f95f330dc5a, < c31f26c8f69f776759cbbdfb38e40ea91aa0dd65 | 5.14

• linux•linux_kernel

  ≥ 5.14, < 5.15.71 | ≥ 5.16, < 5.19.12 | 6.0:rc1 | 6.0:rc2 | 6.0:rc3 | 6.0:rc4 | 6.0:rc5 | 6.0:rc6

References (3)

• https://git.kernel.org/stable/c/08483e4c0c83b221b8891434a04cec405dee94a6
• https://git.kernel.org/stable/c/32afa1f23e42cc635ccf4c39f24514d03d1e8338
• https://git.kernel.org/stable/c/c31f26c8f69f776759cbbdfb38e40ea91aa0dd65