All of lore.kernel.org
 help / color / mirror / Atom feed
* [kernel-cve-report] New CVE entries this week
@ 2024-03-27 23:10 Masami Ichikawa
  0 siblings, 0 replies; 33+ messages in thread
From: Masami Ichikawa @ 2024-03-27 23:10 UTC (permalink / raw)
  To: cip-dev

Hi!

It's this week's CVE report.

This week reported 60 new CVEs and 9 updated CVEs.

* New CVEs

CVE-2023-52620: netfilter: nf_tables: disallow timeout for anonymous sets

Announce: https://lore.kernel.org/linux-cve-announce/2024032147-CVE-2023-52620-11a9@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.4.
It looks as if CVE-2023-52620 and CVE-2024-26642 both have the same root causes.
So, commit 761da29 ("netfilter: nf_tables: add set timeout API
support") may introduce this bug.
The commit 761da29 was merged in 4.1-rc1.

Fixed status
mainline: [e26d3009efda338f19016df4175f354a9bd0a4ab]
stable/5.15: [00b19ee0dcc1aef06294471ab489bae26d94524e]
stable/6.1: [b7be6c737a179a76901c872f6b4c1d00552d9a1b]

CVE-2024-26642: netfilter: nf_tables: disallow anonymous set with timeout flag

Announce: https://lore.kernel.org/linux-cve-announce/2024032150-CVE-2024-26642-3549@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 761da29 ("netfilter: nf_tables: add set timeout
API support") in v4.1-rc1.
Fixed in v6.8.

Fixed status
mainline: [16603605b667b70da974bea8216c93e7db043bf1]

CVE-2024-26643: netfilter: nf_tables: mark set as dead when unbinding
anonymous set with timeout

Announce: https://lore.kernel.org/linux-cve-announce/2024032150-CVE-2024-26643-4f9d@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 5f68718 ("netfilter: nf_tables: GC transaction
API to avoid race with control plane") in v6.5-rc6.
This commit was backported to 5.10, 5.15, 5.4, and 6.1. Linux 4.x is
not affected.
Fixed in v6.8.

Fixed status
mainline: [552705a3650bbf46a22b1adedc1b04181490fc36]

CVE-2021-47136: net: zero-initialize tc skb extension on allocation

Announce: https://lore.kernel.org/linux-cve-announce/2024032553-CVE-2021-47136-407d@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 038ebb1 ("net/sched: act_ct: fix miss set mru for
ovs after defrag in act_ct") in v5.9-rc1.
Introduced by commit d29334c ("net/sched: act_api: fix miss set
post_ct for ovs after do conntrack in act_ct") in v5.12-rc5.
These commits are not backported to older stable kernels.
Fixed in v5.13-rc4.

Fixed status
mainline: [9453d45ecb6c2199d72e73c993e9d98677a2801b]
stable/5.10: [ac493452e937b8939eaf2d24cac51a4804b6c20e]

CVE-2021-47137: net: lantiq: fix memory corruption in RX ring

Announce: https://lore.kernel.org/linux-cve-announce/2024032556-CVE-2021-47137-7c8e@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit fe1a564 ("net: lantiq: Add Lantiq / Intel VRX200
Ethernet driver ") in v4.20-rc1.
This commit is not backported to older stable kernels.
Fixed in v5.13-rc4.

Fixed status
mainline: [c7718ee96dbc2f9c5fc3b578abdf296dd44b9c20]
stable/5.10: [5ac72351655f8b033a2935646f53b7465c903418]
stable/5.4: [8bb1077448d43a871ed667520763e3b9f9b7975d]

CVE-2021-47138: cxgb4: avoid accessing registers when clearing filters

Announce: https://lore.kernel.org/linux-cve-announce/2024032557-CVE-2021-47138-9241@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit b1a7936 ("cxgb4: Delete all hash and TCAM filters
before resource cleanup") in v5.2-rc1.
This commit is not backported to older stable kernels.
Fixed in v5.13-rc4.

Fixed status
mainline: [88c380df84fbd03f9b137c2b9d0a44b9f2f553b0]
stable/5.10: [02f03883fdb10ad7e66717c70ea163a8d27ae6e7]
stable/5.4: [0bf49b3c8d8b3a43ce09f1b2db70e5484d31fcdf]

CVE-2021-47139: net: hns3: put off calling register_netdev() until
client initialize complete

Announce: https://lore.kernel.org/linux-cve-announce/2024032557-CVE-2021-47139-994d@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 08a1006 ("net: hns3: re-organize vector handle")
in v5.6-rc1.
This commit is not backported to older stable kernels.
Fixed in v5.13-rc4.

Fixed status
mainline: [a289a7e5c1d49b7d47df9913c1cc81fb48fab613]
stable/5.10: [a663c1e418a3b5b8e8edfad4bc8e7278c312d6fc]

CVE-2021-47140: iommu/amd: Clear DMA ops when switching domain

Announce: https://lore.kernel.org/linux-cve-announce/2024032557-CVE-2021-47140-5dd4@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 08a27c1 ("iommu: Add support to change default
domain of an iommu group") in v5.11-rc1.
This commit is not backported to older stable kernels.
Fixed in v5.13-rc4.

Fixed status
mainline: [d6177a6556f853785867e2ec6d5b7f4906f0d809]

CVE-2021-47141: gve: Add NULL pointer checks when freeing irqs.

Announce: https://lore.kernel.org/linux-cve-announce/2024032557-CVE-2021-47141-ce47@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 893ce44 ("gve: Add basic driver framework for
Compute Engine Virtual NIC") in v5.3-rc1.
This commit is not backported to older stable kernels.
Fixed in v5.13-rc4.

Fixed status
mainline: [5218e919c8d06279884aa0baf76778a6817d5b93]
stable/5.10: [da21a35c00ff1a1794d4f166d3b3fa8db4d0f6fb]
stable/5.4: [821149ee88c206fa37e79c1868cc270518484876]

CVE-2021-47142: drm/amdgpu: Fix a use-after-free

Announce: https://lore.kernel.org/linux-cve-announce/2024032558-CVE-2021-47142-9319@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v5.13-rc3.
It looks as if it was introduced by commit d38ceaf ("drm/amdgpu: add
core driver (v4)") in 4.2-rc1.

Fixed status
cip/4.4: [0707c3fea8102d211631ba515ef2159707561b0d]
cip/4.4-rt: [0707c3fea8102d211631ba515ef2159707561b0d]
cip/4.4-st: [0707c3fea8102d211631ba515ef2159707561b0d]
mainline: [1e5c37385097c35911b0f8a0c67ffd10ee1af9a2]
stable/4.19: [a849e218556f932576c0fb1c5a88714b61709a17]
stable/4.4: [0707c3fea8102d211631ba515ef2159707561b0d]
stable/5.10: [f98cdf084405333ee2f5be548a91b2d168e49276]
stable/5.4: [7398c2aab4da960761ec182d04d6d5abbb4a226e]

CVE-2021-47143: net/smc: remove device from smcd_dev_list after failed
device_add()

Announce: https://lore.kernel.org/linux-cve-announce/2024032558-CVE-2021-47143-4f3c@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit c6ba7c9 ("net/smc: add base infrastructure for
SMC-D and ISM") in v4.19-rc1.
This commit is not backported to older stable kernels.
Fixed in v5.13-rc4. Linux 4.19 is not fixed yet.

Fixed status
mainline: [444d7be9532dcfda8e0385226c862fd7e986f607]
stable/5.10: [8b2cdc004d21a7255f219706dca64411108f7897]

CVE-2021-47144: drm/amd/amdgpu: fix refcount leak

Announce: https://lore.kernel.org/linux-cve-announce/2024032558-CVE-2021-47144-26d3@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v5.13-rc3.
The obj variable in struct drm_framebuffer is not exist in Linux 4.4
so it may not affect to Linux 4.4.

Fixed status
mainline: [fa7e6abc75f3d491bc561734312d065dc9dc2a77]
stable/4.19: [599e5d61ace952b0bb9bd942b198bbd0cfded1d7]
stable/5.10: [9fdb8ed37a3a44f9c49372b69f87fd5f61cb3240]
stable/5.4: [dde2656e0bbb2ac7d83a7bd95a8d5c3c95bbc009]

CVE-2021-47145: btrfs: do not BUG_ON in link_to_fixup_dir

Announce: https://lore.kernel.org/linux-cve-announce/2024032558-CVE-2021-47145-e536@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v5.13-rc3.

Fixed status
cip/4.4: [76bfd8ac20bebeae599452a03dfc5724c0475dcf]
cip/4.4-rt: [76bfd8ac20bebeae599452a03dfc5724c0475dcf]
cip/4.4-st: [76bfd8ac20bebeae599452a03dfc5724c0475dcf]
mainline: [91df99a6eb50d5a1bc70fff4a09a0b7ae6aab96d]
stable/4.19: [6eccfb28f8dca70c9b1b3bb3194ca54cbe73a9fa]
stable/4.4: [76bfd8ac20bebeae599452a03dfc5724c0475dcf]
stable/5.10: [7e13db503918820e6333811cdc6f151dcea5090a]
stable/5.4: [0ed102453aa1cd12fefde8f6b60b9519b0b1f003]

CVE-2021-47146: mld: fix panic in mld_newpack()

Announce: https://lore.kernel.org/linux-cve-announce/2024032559-CVE-2021-47146-05d4@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 72e09ad ("ipv6: avoid high order allocations") in
v2.6.35-rc3.
Fixed in v5.13-rc4.

Fixed status
cip/4.4: [0e35b7457b7b6e73ffeaaca1a577fdf1af0feca1]
cip/4.4-rt: [0e35b7457b7b6e73ffeaaca1a577fdf1af0feca1]
cip/4.4-st: [0e35b7457b7b6e73ffeaaca1a577fdf1af0feca1]
mainline: [020ef930b826d21c5446fdc9db80fd72a791bc21]
stable/4.19: [4b77ad9097067b31237eeeee0bf70f80849680a0]
stable/4.4: [0e35b7457b7b6e73ffeaaca1a577fdf1af0feca1]
stable/5.10: [beb39adb150f8f3b516ddf7c39835a9788704d23]
stable/5.4: [37d697759958d111439080bab7e14d2b0e7b39f5]

CVE-2021-47147: ptp: ocp: Fix a resource leak in an error handling path

Announce: https://lore.kernel.org/linux-cve-announce/2024032559-CVE-2021-47147-e4bc@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit a7e1aba ("ptp: Add clock driver for the
OpenCompute TimeCard.") in v5.11-rc1.
This commit is not backported to the older stable kernel.
Fixed in v5.13-rc4.

Fixed status
mainline: [9c1bb37f8cad5e2ee1933fa1da9a6baa7876a8e4]

CVE-2021-47148: octeontx2-pf: fix a buffer overflow in otx2_set_rxfh_context()

Announce: https://lore.kernel.org/linux-cve-announce/2024032559-CVE-2021-47148-502f@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 81a4362 ("octeontx2-pf: Add RSS multi group
support") in v5.12-rc1.
This commit is not backported to the older stable kernel.
Fixed in v5.13-rc4.

Fixed status
mainline: [e5cc361e21648b75f935f9571d4003aaee480214]

CVE-2021-47149: net: fujitsu: fix potential null-ptr-deref

Announce: https://lore.kernel.org/linux-cve-announce/2024032500-CVE-2021-47149-b998@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v5.13-rc3.

Fixed status
cip/4.4: [b92170e209f7746ed72eaac98f2c2f4b9af734e6]
cip/4.4-rt: [b92170e209f7746ed72eaac98f2c2f4b9af734e6]
cip/4.4-st: [b92170e209f7746ed72eaac98f2c2f4b9af734e6]
mainline: [52202be1cd996cde6e8969a128dc27ee45a7cb5e]
stable/4.19: [7883d3895d0fbb0ba9bff0f8665f99974b45210f]
stable/4.4: [b92170e209f7746ed72eaac98f2c2f4b9af734e6]
stable/5.10: [71723a796ab7881f491d663c6cd94b29be5fba50]
stable/5.4: [22049c3d40f08facd1867548716a484dad6b3251]

CVE-2021-47150: net: fec: fix the potential memory leak in fec_enet_init()

Announce: https://lore.kernel.org/linux-cve-announce/2024032500-CVE-2021-47150-f066@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 59d0f74 ("net: fec: init multi queue date
structure") in v3.18-rc1.
Linux 4.4 is not fixed yet.
Fixed in v5.13-rc4.

Fixed status
mainline: [619fee9eb13b5d29e4267cb394645608088c28a8]
stable/4.19: [15102886bc8f5f29daaadf2d925591d564c17e9f]
stable/5.10: [8ee7ef4a57a9e1228b6f345aaa70aa8951c7e9cd]
stable/5.4: [20255d41ac560397b6a07d8d87dcc5e2efc7672a]

CVE-2021-47151: interconnect: qcom: bcm-voter: add a missing of_node_put()

Announce: https://lore.kernel.org/linux-cve-announce/2024032500-CVE-2021-47151-2551@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 976daac ("interconnect: qcom: Consolidate
interconnect RPMh support") in v5.7-rc1.
This commit is not backported to older stable kernels.
Fixed in v5.13-rc4.

Fixed status
mainline: [a00593737f8bac2c9e97b696e7ff84a4446653e8]
stable/5.10: [4e3cea8035b6f1b9055e69cc6ebf9fa4e50763ae]

CVE-2021-47152: mptcp: fix data stream corruption

Announce: https://lore.kernel.org/linux-cve-announce/2024032500-CVE-2021-47152-a386@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 18b683b ("mptcp: queue data for mptcp level
retransmission") in v5.7-rc1.
This commit is not backported to older stable kernels.
Fixed in v5.13-rc4.

Fixed status
mainline: [29249eac5225429b898f278230a6ca2baa1ae154]
stable/5.10: [3267a061096efc91eda52c2a0c61ba76e46e4b34]

CVE-2021-47153: i2c: i801: Don't generate an interrupt on bus reset

Announce: https://lore.kernel.org/linux-cve-announce/2024032501-CVE-2021-47153-8c75@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 636752b ("i2c-i801: Enable IRQ for SMBus
transactions") in v3.6-rc1.
Fixed in v5.13-rc4.

Fixed status
cip/4.4: [f9469082126cebb7337db3992d143f5e4edfe629]
cip/4.4-rt: [f9469082126cebb7337db3992d143f5e4edfe629]
cip/4.4-st: [f9469082126cebb7337db3992d143f5e4edfe629]
mainline: [e4d8716c3dcec47f1557024add24e1f3c09eb24b]
stable/4.19: [c70e1ba2e7e65255a0ce004f531dd90dada97a8c]
stable/4.4: [f9469082126cebb7337db3992d143f5e4edfe629]
stable/5.10: [b523feb7e8e44652f92f3babb953a976e7ccbbef]
stable/5.4: [04cc05e3716ae31b17ecdab7bc55c8170def1b8b]

CVE-2021-47158: net: dsa: sja1105: add error handling in sja1105_setup()

Announce: https://lore.kernel.org/linux-cve-announce/2024032533-CVE-2021-47158-71e9@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 0a7bdbc ("net: dsa: sja1105: move devlink param
code to sja1105_devlink.c") in v5.10-rc1.
Introduced by commit 8aa9ebc ("net: dsa: Introduce driver for NXP
SJA1105 5-port L2 switch") in v5.2-rc1.
These commits are not backported to older stable kernels.
Fixed in v5.13-rc4.

Fixed status
mainline: [cec279a898a3b004411682f212215ccaea1cd0fb]
stable/5.10: [dd8609f203448ca6d58ae71461208b3f6b0329b0]

CVE-2021-47159: net: dsa: fix a crash if ->get_sset_count() fails

Announce: https://lore.kernel.org/linux-cve-announce/2024032533-CVE-2021-47159-9ac6@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit badf3ad ("net: dsa: Provide CPU port statistics
to master netdev") in v4.7-rc1.
This commit is not backpoted to 4.4.
Fixed in v5.13-rc4.

Fixed status
mainline: [a269333fa5c0c8e53c92b5a28a6076a28cde3e83]
stable/4.19: [0f2cb08c57edefb0e7b5045e0e3e9980a3d3aa37]
stable/5.10: [caff86f85512b8e0d9830e8b8b0dfe13c68ce5b6]
stable/5.4: [ce5355f140a7987011388c7e30c4f8fbe180d3e8]

CVE-2021-47160: net: dsa: mt7530: fix VLAN traffic leaks

Announce: https://lore.kernel.org/linux-cve-announce/2024032534-CVE-2021-47160-8e53@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 83163f7 ("net: dsa: mediatek: add VLAN support
for MT7530") in v4.16-rc1.
This commit is not backpoted to 4.4.
Fixed in v5.13-rc4.

Fixed status
mainline: [474a2ddaa192777522a7499784f1d60691cd831a]
stable/4.19: [ae389812733b1b1e8e07fcc238e41db166b5c78d]
stable/5.10: [b91117b66fe875723a4e79ec6263526fffdb44d2]
stable/5.4: [4fe4e1f48ba119bdbc7c897c83b04ba0d08f5488]

CVE-2021-47161: spi: spi-fsl-dspi: Fix a resource leak in an error handling path

Announce: https://lore.kernel.org/linux-cve-announce/2024032534-CVE-2021-47161-65ce@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 90ba370 ("spi: spi-fsl-dspi: Add DMA support for
Vybrid") in v4.10-rc1.
This commit is not backpoted to 4.4.
Fixed in v5.13-rc4.

Fixed status
mainline: [680ec0549a055eb464dce6ffb4bfb736ef87236e]
stable/4.19: [00450ed03a17143e2433b461a656ef9cd17c2f1d]
stable/5.10: [fe6921e3b8451a537e01c031b8212366bb386e3e]
stable/5.4: [15d1cc4b4b585f9a2ce72c52cca004d5d735bdf1]

CVE-2021-47162: tipc: skb_linearize the head skb when reassembling msgs

Announce: https://lore.kernel.org/linux-cve-announce/2024032534-CVE-2021-47162-01da@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 45c8b7b ("tipc: allow non-linear first fragment
buffer") in v4.3.
Fixed in v5.13-rc4.

Fixed status
cip/4.4: [b2c8d28c34b3070407cb1741f9ba3f15d0284b8b]
cip/4.4-rt: [b2c8d28c34b3070407cb1741f9ba3f15d0284b8b]
cip/4.4-st: [b2c8d28c34b3070407cb1741f9ba3f15d0284b8b]
mainline: [b7df21cf1b79ab7026f545e7bf837bd5750ac026]
stable/4.19: [4b1761898861117c97066aea6c58f68a7787f0bf]
stable/4.4: [b2c8d28c34b3070407cb1741f9ba3f15d0284b8b]
stable/5.10: [6da24cfc83ba4f97ea44fc7ae9999a006101755c]
stable/5.4: [64d17ec9f1ded042c4b188d15734f33486ed9966]

CVE-2021-47163: tipc: wait and exit until all work queues are done

Announce: https://lore.kernel.org/linux-cve-announce/2024032534-CVE-2021-47163-3ab9@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit d0f9193 ("tipc: add ip/udp media type") in v4.1-rc1.
Fixed in v5.13-rc4.
Backporting this fix to 4.19 and 4.4 ware failed.
4.19: https://lore.kernel.org/stable/162238534421917@kroah.com/
4.4: https://lore.kernel.org/stable/162238339320326@kroah.com/

Fixed status
mainline: [04c26faa51d1e2fe71cf13c45791f5174c37f986]
stable/5.10: [5195ec5e365a2a9331bfeb585b613a6e94f98dba]
stable/5.4: [d1f76dfadaf8f47ed1753f97dbcbd41c16215ffa]

CVE-2021-47164: net/mlx5e: Fix null deref accessing lag dev

Announce: https://lore.kernel.org/linux-cve-announce/2024032535-CVE-2021-47164-0581@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 7e51891 ("net/mlx5e: Use netdev events to set/del
egress acl forward-to-vport rule") in v5.8-rc1.
This commit is not backported to older stable kernels.
Fixed in v5.13-rc4.

Fixed status
mainline: [83026d83186bc48bb41ee4872f339b83f31dfc55]
stable/5.10: [2e4b0b95a489259f9d35a3db17023061f8f3d587]

CVE-2021-47165: drm/meson: fix shutdown crash when component not probed

Announce: https://lore.kernel.org/linux-cve-announce/2024032535-CVE-2021-47165-95d9@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit fa0c16c ("drm: meson_drv add shutdown function")
in v5.12-rc3.
This commit was backported to 4.19, 5.10, and 5.4. Linux 4.4 is not affected.
Fixed in v5.13-rc4.

Fixed status
mainline: [7cfc4ea78fc103ea51ecbacd9236abb5b1c490d2]
stable/4.19: [e256a0eb43e17209e347409a80805b1659398d68]
stable/5.10: [d66083c0d6f5125a4d982aa177dd71ab4cd3d212]
stable/5.4: [4ce2bf20b4a6e307e114847d60b2bf40a6a1fac0]

CVE-2021-47166: NFS: Don't corrupt the value of pg_bytes_written in
nfs_do_recoalesce()

Announce: https://lore.kernel.org/linux-cve-announce/2024032535-CVE-2021-47166-6ab7@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit a7d42dd ("nfs: add mirroring support to pgio
layer") in v4.0-rc1.
Fixed in v5.13-rc4.

Fixed status
cip/4.4: [e8b8418ce14ae66ee55179901edd12191ab06a9e]
cip/4.4-rt: [e8b8418ce14ae66ee55179901edd12191ab06a9e]
cip/4.4-st: [e8b8418ce14ae66ee55179901edd12191ab06a9e]
mainline: [0d0ea309357dea0d85a82815f02157eb7fcda39f]
stable/4.19: [40f139a6d50c232c0d1fd1c5e65a845c62db0ede]
stable/4.4: [e8b8418ce14ae66ee55179901edd12191ab06a9e]
stable/5.10: [7087db95c0a06ab201b8ebfac6a7ec1e34257997]
stable/5.4: [785917316b25685c9b3a2a88f933139f2de75e33]

CVE-2021-47167: NFS: Fix an Oopsable condition in __nfs_pageio_add_request()

Announce: https://lore.kernel.org/linux-cve-announce/2024032535-CVE-2021-47167-c68c@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit a7d42dd ("nfs: add mirroring support to pgio
layer") in v4.0-rc1.
Fixed in v5.13-rc4.
Backporting this fix to 4.19
(https://lore.kernel.org/stable/162238258072199@kroah.com/) and 4.4
(https://lore.kernel.org/stable/162238257828195@kroah.com/)
were failed.

Fixed status
mainline: [56517ab958b7c11030e626250c00b9b1a24b41eb]
stable/5.10: [ee21cd3aa8548e0cbc8c67a80b62113aedd2d101]
stable/5.4: [1fc5f4eb9d31268ac3ce152d74ad5501ad24ca3e]

CVE-2021-47168: NFS: fix an incorrect limit in filelayout_decode_layout()

Announce: https://lore.kernel.org/linux-cve-announce/2024032536-CVE-2021-47168-2916@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 16b374c ("NFSv4.1: pnfs: filelayout: add driver's
LAYOUTGET and GETDEVICEINFO infrastructure") in v2.6.37-rc1.
Fixed in v5.13-rc4.

Fixed status
cip/4.4: [9d280ab53df1d4a1043bd7a9e7c6a2f9cfbfe040]
cip/4.4-rt: [9d280ab53df1d4a1043bd7a9e7c6a2f9cfbfe040]
cip/4.4-st: [9d280ab53df1d4a1043bd7a9e7c6a2f9cfbfe040]
mainline: [769b01ea68b6c49dc3cde6adf7e53927dacbd3a8]
stable/4.19: [945ebef997227ca8c20bad7f8a8358c8ee57a84a]
stable/4.4: [9d280ab53df1d4a1043bd7a9e7c6a2f9cfbfe040]
stable/5.10: [9b367fe770b1b80d7bf64ed0d177544a44405f6e]
stable/5.4: [e411df81cd862ef3d5b878120b2a2fef0ca9cdb1]

CVE-2021-47169: serial: rp2: use 'request_firmware' instead of
'request_firmware_nowait'

Announce: https://lore.kernel.org/linux-cve-announce/2024032536-CVE-2021-47169-4fd2@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v5.13-rc4.

Fixed status
cip/4.4: [1e04d5d5fe5e76af68f834e1941fcbfa439653be]
cip/4.4-rt: [1e04d5d5fe5e76af68f834e1941fcbfa439653be]
cip/4.4-st: [1e04d5d5fe5e76af68f834e1941fcbfa439653be]
mainline: [016002848c82eeb5d460489ce392d91fe18c475c]
stable/4.19: [35265552c7fe9553c75e324c80f45e28ff14eb6e]
stable/4.4: [1e04d5d5fe5e76af68f834e1941fcbfa439653be]
stable/5.10: [6a931ceb0b9401fe18d0c500e08164bf9cc7be4b]
stable/5.4: [915452f40e2f495e187276c4407a4f567ec2307e]

CVE-2021-47170: USB: usbfs: Don't WARN about excessively large memory
allocations

Announce: https://lore.kernel.org/linux-cve-announce/2024032536-CVE-2021-47170-ee51@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v5.13-rc4.
It looks as if Linux 4.4 may be affected.

Fixed status
mainline: [4f2629ea67e7225c3fd292c7fe4f5b3c9d6392de]
stable/4.19: [2ab21d6e1411999b5fb43434f421f00bf50002eb]
stable/5.10: [8d83f109e920d2776991fa142bb904d985dca2ed]
stable/5.4: [2c835fede13e03f2743a333e4370b5ed2db91e83]

CVE-2021-47171: net: usb: fix memory leak in smsc75xx_bind

Announce: https://lore.kernel.org/linux-cve-announce/2024032536-CVE-2021-47171-f223@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit d0cad87 ("smsc75xx: SMSC LAN75xx USB gigabit
ethernet adapter driver") in v2.6.34-rc2.
Fixed in v5.13-rc4.

Fixed status
cip/4.4: [200dbfcad8011e50c3cec269ed7b980836eeb1fa]
cip/4.4-rt: [200dbfcad8011e50c3cec269ed7b980836eeb1fa]
cip/4.4-st: [200dbfcad8011e50c3cec269ed7b980836eeb1fa]
mainline: [46a8b29c6306d8bbfd92b614ef65a47c900d8e70]
stable/4.19: [9e6a3eccb28779710cbbafc4f4258d92509c6d07]
stable/4.4: [200dbfcad8011e50c3cec269ed7b980836eeb1fa]
stable/5.10: [635ac38b36255d3cfb8312cf7c471334f4d537e0]
stable/5.4: [b95fb96e6339e34694dd578fb6bde3575b01af17]

CVE-2021-47172: iio: adc: ad7124: Fix potential overflow due to non
sequential channel numbers

Announce: https://lore.kernel.org/linux-cve-announce/2024032537-CVE-2021-47172-4990@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit d7857e4 ("iio: adc: ad7124: Fix DT channel
configuration") in v5.5-rc7.
This commit was backported to 5.4. Linux 4.x is not affected.
Fixed in v5.13-rc4.

Fixed status
mainline: [f2a772c51206b0c3f262e4f6a3812c89a650191b]
stable/5.10: [f70122825076117787b91e7f219e21c09f11a5b9]
stable/5.4: [f49149964d2423fb618fb6b755bb1eaa431cca2c]

CVE-2021-47173: misc/uss720: fix memory leak in uss720_probe

Announce: https://lore.kernel.org/linux-cve-announce/2024032537-CVE-2021-47173-12cc@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 0f36163 ("[PATCH] usb: fix uss720 schedule with
interrupts off") in v2.6.20.16.
Fixed in v5.13-rc4.

Fixed status
cip/4.4: [5f46b2410db2c8f26b8bb91b40deebf4ec184391]
cip/4.4-rt: [5f46b2410db2c8f26b8bb91b40deebf4ec184391]
cip/4.4-st: [5f46b2410db2c8f26b8bb91b40deebf4ec184391]
mainline: [dcb4b8ad6a448532d8b681b5d1a7036210b622de]
stable/4.19: [386918878ce4cd676e4607233866e03c9399a46a]
stable/4.4: [5f46b2410db2c8f26b8bb91b40deebf4ec184391]
stable/5.10: [5394ae9d8c7961dd93807fdf1b12a1dde96b0a55]
stable/5.4: [36b5ff1db1a4ef4fdbc2bae364344279f033ad88]

CVE-2021-47174: netfilter: nft_set_pipapo_avx2: Add irq_fpu_usable()
check, fallback to non-AVX2 version

Announce: https://lore.kernel.org/linux-cve-announce/2024032537-CVE-2021-47174-a330@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 7400b06 ("nft_set_pipapo: Introduce AVX2-based
lookup implementation") in v5.7-rc1.
This commit is not backported to older stable kernels.
Fixed in v5.13-rc4.

Fixed status
mainline: [f0b3d338064e1fe7531f0d2977e35f3b334abfb4]
stable/5.10: [b1f45a26bd322525c14edd9504f6d46dfad679a4]

CVE-2021-47175: net/sched: fq_pie: fix OOB access in the traffic path

Announce: https://lore.kernel.org/linux-cve-announce/2024032537-CVE-2021-47175-5b85@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit ec97ecf ("net: sched: add Flow Queue PIE packet
scheduler") in v5.6-rc1.
This commit is not backported to older stable kernels.
Fixed in v5.13-rc4.

Fixed status
mainline: [e70f7a11876a1a788ceadf75e9e5f7af2c868680]
stable/5.10: [e6294c06e7c62ffdd5bf3df696d3a4fcbb753d3c]

CVE-2021-47176: s390/dasd: add missing discipline function

Announce: https://lore.kernel.org/linux-cve-announce/2024032538-CVE-2021-47176-015a@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit b729493 ("s390/dasd: Prepare for additional path
event handling") in v5.11-rc1.
This commit was backported to 5.10 and 5.4. Linux 4.4 is not affected.
Fixed in v5.13-rc4.

Fixed status
mainline: [c0c8a8397fa8a74d04915f4d3d28cb4a5d401427]
stable/5.10: [aa8579bc084673c651204f7cd0d6308a47dffc16]
stable/5.4: [6a16810068e70959bc1df686424aa35ce05578f1]

CVE-2021-47177: iommu/vt-d: Fix sysfs leak in alloc_iommu()

Announce: https://lore.kernel.org/linux-cve-announce/2024032538-CVE-2021-47177-4d4a@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 39ab955 ("iommu: Add sysfs bindings for struct
iommu_device") in v4.11-rc1.
This commit is not backported to older stable kernels.
Fixed in v5.13-rc4.

Fixed status
mainline: [0ee74d5a48635c848c20f152d0d488bf84641304]
stable/4.19: [2ec5e9bb6b0560c90d315559c28a99723c80b996]
stable/5.10: [f01134321d04f47c718bb41b799bcdeda27873d2]
stable/5.4: [044bbe8b92ab4e542de7f6c93c88ea65cccd8e29]

CVE-2021-47178: scsi: target: core: Avoid smp_processor_id() in preemptible code

Announce: https://lore.kernel.org/linux-cve-announce/2024032538-CVE-2021-47178-6167@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 1526d9f ("scsi: target: Make state_list per CPU")
in v5.11-rc1.
This commit was backported to 5.10. Linux 5.4 and 4.x are not affected.
Fixed in v5.13-rc4.

Fixed status
mainline: [70ca3c57ff914113f681e657634f7fbfa68e1ad1]
stable/5.10: [a222d2794c53f8165de20aa91b39e35e4b72bce9]

CVE-2021-47179: NFSv4: Fix a NULL pointer dereference in
pnfs_mark_matching_lsegs_return()

Announce: https://lore.kernel.org/linux-cve-announce/2024032538-CVE-2021-47179-d9c2@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit de144ff ("NFSv4: Don't discard segments marked
for return in _pnfs_return_layout()") in 5.13-rc1.
This commit was backported to 4.19, 5.10, and 5.4. Linux 4.4 is not affected.
Fixed in 5.13-rc4.

Fixed status
mainline: [a421d218603ffa822a0b8045055c03eae394a7eb]
stable/4.19: [39785761feadf261bc5101372b0b0bbaf6a94494]
stable/5.10: [f9890652185b72b8de9ebeb4406037640b6e1b53]
stable/5.4: [aba3c7795f51717ae316f3566442dee7cc3eeccb]

CVE-2021-47180: NFC: nci: fix memory leak in nci_allocate_device

Announce: https://lore.kernel.org/linux-cve-announce/2024032539-CVE-2021-47180-5b80@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 11f54f2 ("NFC: nci: Add HCI over NCI protocol
support") in v4.0-rc1.
Fixed in v5.13-rc4.

Fixed status
cip/4.4: [448a1cb12977f52142e6feb12022c59662d88dc1]
cip/4.4-rt: [448a1cb12977f52142e6feb12022c59662d88dc1]
cip/4.4-st: [448a1cb12977f52142e6feb12022c59662d88dc1]
mainline: [e0652f8bb44d6294eeeac06d703185357f25d50b]
stable/4.19: [0365701bc44e078682ee1224866a71897495c7ef]
stable/4.4: [448a1cb12977f52142e6feb12022c59662d88dc1]
stable/5.10: [b34cb7ac32cc8e5471dc773180ea9ae676b1a745]
stable/5.4: [af2a4426baf71163c0c354580ae98c7888a9aba7]

CVE-2023-52621: bpf: Check rcu_read_lock_trace_held() before calling
bpf map helpers

Announce: https://lore.kernel.org/linux-cve-announce/20240326171931.1354035-4-lee@kernel.org/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc1.

The sleepable bpf program feature was introduced by commit 1e6c62a88
("bpf: Introduce sleepable BPF programs") in 5.10-rc1.
So, Linux 5.4 and 4.x are not affected.

Fixed status
mainline: [169410eba271afc9f0fb476d996795aa26770c6d]
stable/6.1: [d6d6fe4bb105595118f12abeed4a7bdd450853f3]
stable/6.6: [483cb92334cd7f1d5387dccc0ab5d595d27a669d]
stable/6.7: [c7f1b6146f4a46d727c0d046284c28b6882c6304]

CVE-2023-52622: ext4: avoid online resizing failures due to oversized flex bg

Announce: https://lore.kernel.org/linux-cve-announce/20240326171931.1354035-5-lee@kernel.org/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc1.
Linux 4.4 seems to be affected.

Fixed status
mainline: [5d1935ac02ca5aee364a449a35e2977ea84509b0]
stable/4.19: [cd1f93ca97a9136989f3bd2bf90696732a2ed644]
stable/5.10: [cfbbb3199e71b63fc26cee0ebff327c47128a1e8]
stable/5.15: [d76c8d7ffe163c6bf2f1ef680b0539c2b3902b90]
stable/5.4: [b183fe8702e78bba3dcef8e7193cab6898abee07]
stable/6.1: [6d2cbf517dcabc093159cf138ad5712c9c7fa954]
stable/6.6: [8b1413dbfe49646eda2c00c0f1144ee9d3368e0c]
stable/6.7: [dc3e0f55bec4410f3d74352c4a7c79f518088ee2]

CVE-2023-52623: SUNRPC: Fix a suspicious RCU usage warning

Announce: https://lore.kernel.org/linux-cve-announce/20240326171931.1354035-6-lee@kernel.org/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc1.
The rpc_xprt_switch_has_addr() was introduced by commit 39e5d2df
("SUNRPC search xprt switch for sockaddr") in 4.9-rc1.
Linux 4.4 is not affected.

Fixed status
mainline: [31b62908693c90d4d07db597e685d9f25a120073]
stable/4.19: [fece80a2a6718ed58487ce397285bb1b83a3e54e]
stable/5.10: [c430e6bb43955c6bf573665fcebf31694925b9f7]
stable/5.15: [f8cf4dabbdcb8bef85335b0ed7ad5b25fd82ff56]
stable/5.4: [7a96d85bf196c170dcf1b47a82e9bb97cca69aa6]
stable/6.1: [e8ca3e73301e23e8c0ac0ce2e6bac4545cd776e0]
stable/6.6: [69c7eeb4f622c2a28da965f970f982db171f3dc6]
stable/6.7: [8f860c8407470baff2beb9982ad6b172c94f1d0a]

CVE-2023-52624: drm/amd/display: Wake DMCUB before executing GPINT commands

Announce: https://lore.kernel.org/linux-cve-announce/20240326175007.1388794-10-lee@kernel.org/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc1.
Backporting this fix to 6.1 failed
(https://lore.kernel.org/stable/2024012756-pauper-underdog-470b@gregkh/).
The dc_dmub_srv.h and dc_dmub_srv.c were introduced by commit
3a1627b073 ("drm/amd/display: Add DMUB support to DC") in 5.6-rc1.
The dmub_psr.c was introduced by commit 4c1a1335d ("drm/amd/display:
Driverside changes to support PSR in DMCUB") in 5.6-rc1.
Therefore, it looks as if 5.4 and 4.x are not affected.

Fixed status
mainline: [e5ffd1263dd5b44929c676171802e7b6af483f21]
stable/6.7: [2ef98c6d753a744e333b7e34b9cf687040fba57d]

CVE-2023-52625: drm/amd/display: Refactor DMCUB enter/exit idle interface

Announce: https://lore.kernel.org/linux-cve-announce/20240326175007.1388794-11-lee@kernel.org/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc1.
Backporting this fix to 6.1 was failed
(https://lore.kernel.org/stable/2024012743-shortcake-unsure-ebfd@gregkh/).

The dc_dmub_srv.h and dc_dmub_srv.c were introduced by commit
3a1627b073 ("drm/amd/display: Add DMUB support to DC") in 5.6-rc1.
The dcn35_hwseq.c was introduced by commit 6f8b7565 ("drm/amd/display:
Add DCN35 HWSEQ").
So that it looks as if at least prior to Linux 5.6 kernels are not affected.

Fixed status
mainline: [8e57c06bf4b0f51a4d6958e15e1a99c9520d00fa]
stable/6.7: [820c3870c491946a78950cdf961bf40e28c1025f]

CVE-2023-52626: net/mlx5e: Fix operation precedence bug in port
timestamping napi_poll context

Announce: https://lore.kernel.org/linux-cve-announce/20240326175007.1388794-12-lee@kernel.org/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 92214be ("net/mlx5e: Update doorbell for port
timestamping CQ before the software counter") in v6.7-rc2.
This commit was backported to 6.6. Prior to Linux 6.6 kernels are not affected.
Fixed in v6.8-rc2.

Fixed status
mainline: [3876638b2c7ebb2c9d181de1191db0de8cac143a]
stable/6.6: [40e0d0746390c5b0c31144f4f1688d72f3f8d790]
stable/6.7: [33cdeae8c6fb58cc445f859b67c014dc9f60b4e0]

CVE-2023-52627: iio: adc: ad7091r: Allow users to configure device events

Announce: https://lore.kernel.org/linux-cve-announce/20240326175007.1388794-13-lee@kernel.org/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit ca69300 ("iio: adc: Add support for AD7091R5
ADC") in v5.6-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc1.

Fixed status
mainline: [020e71c7ffc25dfe29ed9be6c2d39af7bd7f661f]
stable/5.10: [1eba6f7ffa295a0eec098c107043074be7cc4ec5]
stable/5.15: [49f322ce1f265935f15e5512da69a399f27a5091]
stable/6.1: [137568aa540a9f587c48ff7d4c51cdba08cfe9a4]
stable/6.6: [89c4e63324e208a23098f7fb15c00487cecbfed2]
stable/6.7: [55aca2ce91a63740278502066beaddbd841af9c6]

CVE-2024-26644: btrfs: don't abort filesystem when attempting to
snapshot deleted subvolume

Announce: https://lore.kernel.org/linux-cve-announce/20240326151722.1258576-3-lee@kernel.org/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc2.
Backporting this fix to 5.4
(https://lore.kernel.org/stable/2024012747-marshland-overcoat-1e01@gregkh/)
and
4.19 (https://lore.kernel.org/stable/2024012750-shore-gradually-d4bb@gregkh/)
were failed.
It looks like Linux 4.4 is affected.

Fixed status
mainline: [7081929ab2572920e94d70be3d332e5c9f97095a]
stable/5.10: [2bdf872bcfe629a6202ffd6641615a8ed00e8464]
stable/5.15: [0877497dc97834728e1b528ddf1e1c484292c29c]
stable/6.1: [6e6bca99e8d88d989a7cde4c064abea552d5219b]
stable/6.6: [ec794a7528199e1be6d47bec03f4755aa75df256]
stable/6.7: [d8680b722f0ff6d7a01ddacc1844e0d52354d6ff]

CVE-2024-26645: tracing: Ensure visibility when inserting an element
into tracing_map

Announce: https://lore.kernel.org/linux-cve-announce/20240326151722.1258576-4-lee@kernel.org/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit c193707 ("tracing: Remove code which merges
duplicates") in v4.17-rc1.
Linux 4.4 is not affected.
Fixed in v6.8-rc2.

Fixed status
mainline: [2b44760609e9eaafc9d234a6883d042fc21132a7]
stable/4.19: [5022b331c041e8c54b9a6a3251579bd1e8c0fc0b]
stable/5.10: [ef70dfa0b1e5084f32635156c9a5c795352ad860]
stable/5.15: [aef1cb00856ccfd614467cfb50b791278992e177]
stable/5.4: [dad9b28f675ed99b4dec261db2a397efeb80b74c]
stable/6.1: [f4f7e696db0274ff560482cc52eddbf0551d4b7a]
stable/6.6: [a1eebe76e187dbe11ca299f8dbb6e45d5b1889e7]
stable/6.7: [bf4aeff7da85c3becd39fb73bac94122331c30fb]

CVE-2024-26646: thermal: intel: hfi: Add syscore callbacks for system-wide PM

Announce: https://lore.kernel.org/linux-cve-announce/20240326175007.1388794-14-lee@kernel.org/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc1.
This driver was introduced by commit 1cb19cabeb ("thermal: intel: hfi:
Minimally initialize the Hardware Feedback Interface") in 5.18-rc1.
So, prior to Linux 5.18 kernels are not affected.

Fixed status
mainline: [97566d09fd02d2ab329774bb89a2cdf2267e86d9]
stable/6.1: [28f010dc50df0f7987c04112114fcfa7e0803566]
stable/6.6: [019ccc66d56a696a4dfee3bfa2f04d0a7c3d89ee]
stable/6.7: [c9d6d63b6c03afaa6f185df249af693a7939577c]

CVE-2024-26647: drm/amd/display: Fix late derefrence 'dsc' check in
'link_set_dsc_pps_packet()'

Announce: https://lore.kernel.org/linux-cve-announce/20240326175007.1388794-15-lee@kernel.org/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc1.

Fixed status
mainline: [3bb9b1f958c3d986ed90a3ff009f1e77e9553207]
stable/6.6: [6aa5ede6665122f4c8abce3c6eba06b49e54d25c]
stable/6.7: [cf656fc7276e5b3709a81bc9d9639459be2b2647]

CVE-2024-26648: drm/amd/display: Fix variable deferencing before NULL
check in edp_setup_replay()

Announce: https://lore.kernel.org/linux-cve-announce/20240326175007.1388794-16-lee@kernel.org/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc1.
The link_dpms.c was introduced by commit 54618888 ("drm/amd/display:
break down dc_link.c") in 6.3-rc1.

Fixed status
mainline: [7073934f5d73f8b53308963cee36f0d389ea857c]
stable/6.6: [22ae604aea14756954e1c00ae653e34d2afd2935]
stable/6.7: [c02d257c654191ecda1dc1af6875d527e85310e7]

CVE-2024-26649: drm/amdgpu: Fix the null pointer when load rlc firmware

Announce: https://lore.kernel.org/linux-cve-announce/20240326175007.1388794-17-lee@kernel.org/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 3da9b71 ("drm/amd: Use `amdgpu_ucode_*` helpers
for GFX10") in v6.3-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc1.

Fixed status
mainline: [bc03c02cc1991a066b23e69bbcc0f66e8f1f7453]
stable/6.6: [8b5bacce2d13dbe648f0bfd3f738ecce8db4978c]
stable/6.7: [d3887448486caeef9687fb5dfebd4ff91e0f25aa]

CVE-2024-26650: platform/x86: p2sb: Allow p2sb_bar() calls during PCI
device probe

Announce: https://lore.kernel.org/linux-cve-announce/20240326175007.1388794-18-lee@kernel.org/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 9745fb0 ("platform/x86/intel: Add Primary to
Sideband (P2SB) bridge support") in v6.0-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc2.

Fixed status
mainline: [5913320eb0b3ec88158cfcb0fa5e996bf4ef681b]
stable/6.1: [2841631a03652f32b595c563695d0461072e0de4]
stable/6.6: [847e1eb30e269a094da046c08273abe3f3361cf2]
stable/6.7: [d281ac9a987c553d93211b90fd4fe97d8eca32cd]

CVE-2024-26651: sr9800: Add check for usbnet_get_endpoints

Announce: https://lore.kernel.org/linux-cve-announce/2024032721-CVE-2024-26651-34b3@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 19a38d8 ("USB2NET : SR9800 : One chip USB2.0
USB2NET SR9800 Device Driver Support") in v3.14-rc3.
Fixed in v6.9-rc1.

Fixed status
mainline: [07161b2416f740a2cb87faa5566873f401440a61]
stable/4.19: [424eba06ed405d557077339edb19ce0ebe39e7c7]
stable/5.10: [6b4a39acafaf0186ed8e97c16e0aa6fca0e52009]
stable/5.15: [276873ae26c8d75b00747c1dadb9561d6ef20581]
stable/5.4: [8a8b6a24684bc278036c3f159f7b3a31ad89546a]
stable/6.1: [9c402819620a842cbfe39359a3ddfaac9adc8384]
stable/6.6: [e39a3a14eafcf17f03c037290b78c8f483529028]
stable/6.7: [efba65777f98457773c5b65e3135c6132d3b015f]

CVE-2024-26652: net: pds_core: Fix possible double free in error handling path

Announce: https://lore.kernel.org/linux-cve-announce/2024032713-CVE-2024-26652-f95c@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 4569cce ("pds_core: add auxiliary_bus devices")
in v6.4-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8.

Fixed status
mainline: [ba18deddd6d502da71fd6b6143c53042271b82bd]
stable/6.6: [995f802abff209514ac2ee03b96224237646cec3]
stable/6.7: [ffda0e962f270b3ec937660afd15b685263232d3]

* Updated CVEs

CVE-2023-52447: bpf: Defer the free of inner map when necessary

stable 5.10 and 5.15 were fixed.

Fixed status
mainline: [876673364161da50eed6b472d746ef88242b2368]
stable/5.10: [90c445799fd1dc214d7c6279c144e33a35e29ef2]
stable/5.15: [37d98fb9c3144c0fddf7f6e99aece9927ac8dce6]
stable/6.1: [62fca83303d608ad4fec3f7428c8685680bb01b0]
stable/6.6: [f91cd728b10c51f6d4a39957ccd56d1e802fc8ee]
stable/6.7: [bfd9b20c4862f41d4590fde11d70a5eeae53dcc5]

CVE-2023-6270: AoE: improper reference count leads to use-after-free
vulnerability

This bug was introduced commit 7562f876c ("[NET]: Rework dev_base via
list_head (v3)") in 2.6.22-rc1.
All stable kernels were fixed.

Fixed status
mainline: [f98364e926626c678fb4b9004b75cacf92ff0662]
stable/4.19: [ad80c34944d7175fa1f5c7a55066020002921a99]
stable/5.10: [faf0b4c5e00bb680e8e43ac936df24d3f48c8e65]
stable/5.15: [7dd09fa80b0765ce68bfae92f4e2f395ccf0fba4]
stable/5.4: [1a54aa506b3b2f31496731039e49778f54eee881]
stable/6.1: [74ca3ef68d2f449bc848c0a814cefc487bf755fa]
stable/6.6: [eb48680b0255a9e8a9bdc93d6a55b11c31262e62]
stable/6.7: [079cba4f4e307c69878226fdf5228c20aa1c969c]
stable/6.8: [a16fbb80064634b254520a46395e36b87ca4731e]

CVE-2024-22099: NULL pointer dereference bug and buffer overflow
vulnerabilities was found in the bluetooth subsystem

All stable kernels were fixed.

Fixed status
mainline: [2535b848fa0f42ddff3e5255cf5e742c9b77bb26]
stable/4.19: [369f419c097e82407dd429a202cde9a73d3ae29b]
stable/5.10: [81d7d920a22fd58ef9aedb1bd0a68ee32bd23e96]
stable/5.15: [8d1753973f598531baaa2c1033cf7f7b5bb004b0]
stable/5.4: [5f369efd9d963c1f711a06c9b8baf9f5ce616d85]
stable/6.1: [567c0411dc3b424fc7bd1e6109726d7ba32d4f73]
stable/6.6: [3ead59bafad05f2967ae2438c0528d53244cfde5]
stable/6.7: [5f9fe302dd3a9bbc50f4888464c1773f45166bfd]

CVE-2023-7042: wifi: ath10k: fix NULL pointer dereference in
ath10k_wmi_tlv_op_pull_mgmt_tx_compl_ev()

stable 4.19, 5.x, and 6.x were fixed.

Fixed status
mainline: [ad25ee36f00172f7d53242dc77c69fff7ced0755]
stable/4.19: [0cd3b0a1dc987697cba1fe93c784365aa1f8a230]
stable/5.10: [e1dc7aa814a95aeeb1b2c05be2b62af8423b15cc]
stable/5.15: [4c4e592266b6eec748ce90e82bd9cbc9838f3633]
stable/5.4: [88a9dffaec779504ab3680d33cf677741c029420]
stable/6.1: [90f089d77e38db1c48629f111f3c8c336be1bc38]
stable/6.6: [10a342fa2fe4c4dd22f2c8fe917d3b1929582076]
stable/6.7: [db755cf93f5895bbac491d27a8e2fe04c5f9ae4a]
stable/6.8: [835c5d37f4b0ba99e9ec285ffa645bc532714191]

Currently tracking CVEs

CVE-2021-31615: Unencrypted Bluetooth Low Energy baseband links in
Bluetooth Core Specifications 4.0 through 5.2

There is no fix information.

CVE-2020-26556: kernel: malleable commitment Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26557: kernel: predictable Authvalue in Bluetooth Mesh
Provisioning Leads to MITM

No fix information.

CVE-2020-26559: kernel: Authvalue leak in Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26560: kernel: impersonation attack in Bluetooth Mesh Provisioning

No fix information.

Regards,
-- 
Masami Ichikawa
Cybertrust Japan Co., Ltd.

Email :masami.ichikawa@cybertrust.co.jp
          :masami.ichikawa@miraclelinux.com


^ permalink raw reply	[flat|nested] 33+ messages in thread

* [kernel-cve-report] New CVE entries this week
@ 2024-05-08 23:45 Masami Ichikawa
  0 siblings, 0 replies; 33+ messages in thread
From: Masami Ichikawa @ 2024-05-08 23:45 UTC (permalink / raw)
  To: cip-dev

Hi!

It's this week's CVE report.

This week reported 32 new CVEs and 28 updated CVEs.

* New CVEs

CVE-2022-48670: peci: cpu: Fix use-after-free in adev_release()

Announce: https://lore.kernel.org/linux-cve-announce/2024050314-CVE-2022-48670-f9f1@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.0-rc4.
It seems to be commit 93e1821 ("peci: Add peci-cpu driver") in
5.18-rc1 introduced this bug.
Bug introduced commit is not backported to older stable kernels

Fixed status
mainline: [1c11289b34ab67ed080bbe0f1855c4938362d9cf]

CVE-2022-48671: cgroup: Add missing cpus_read_lock() to cgroup_attach_task_all()

Announce: https://lore.kernel.org/linux-cve-announce/2024050317-CVE-2022-48671-fbdd@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

This bug was introduced by commit 4f7e723 ("cgroup: Fix
threadgroup_rwsem <-> cpus_read_lock() deadlock") in 6.0-rc3.
Bug introduced commit was backported to following branches.
cip/4.19 cip/4.19-rt cip/5.10 cip/5.10-rt stable/4.19 stable/5.10
stable/5.15 stable/5.4

Fixed status
mainline: [43626dade36fa74d3329046f4ae2d7fdefe401c6]
stable/4.19: [321488cfac7d0eb6d97de467015ff754f85813ff]
stable/5.10: [07191f984842d50020789ff14c75da436a7f46a9]
stable/5.15: [9f267393b036f1470fb12fb892d59e7ff8aeb58d]
stable/5.4: [321488cfac7d0eb6d97de467015ff754f85813ff]

CVE-2022-48672: of: fdt: fix off-by-one error in unflatten_dt_nodes()

Announce: https://lore.kernel.org/linux-cve-announce/2024050318-CVE-2022-48672-b6d9@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 78c44d9 ("drivers/of: Fix depth when unflattening
devicetree") in v4.7-rc1.
Fixed in v6.0-rc6.
Bug introduced commit is not backported to older stable kernels

Fixed status
mainline: [2f945a792f67815abca26fa8a5e863ccf3fa1181]
stable/4.19: [2566706ac6393386a4e7c4ce23fe17f4c98d9aa0]
stable/5.10: [ee4369260e77821602102dcc7d792de39a56365c]
stable/5.15: [ba6b9f7cc1108bad6e2c53b1d6e0156379188db7]
stable/5.4: [e0e88c25f88b9805572263c9ed20f1d88742feaf]

CVE-2022-48673: net/smc: Fix possible access to freed memory in link clear

Announce: https://lore.kernel.org/linux-cve-announce/2024050318-CVE-2022-48673-1692@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit bd4ad57 ("smc: initialize IB transport incl. PD,
MR, QP, CQ, event, WR") in v4.11-rc1.
Fixed in v6.0-rc5.
Bug introduced commit is not backported to older stable kernels

Fixed status
mainline: [e9b1a4f867ae9c1dbd1d71cd09cbdb3239fb4968]

CVE-2022-48674: erofs: fix pcluster use-after-free on UP platforms

Announce: https://lore.kernel.org/linux-cve-announce/2024050318-CVE-2022-48674-b876@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 73f5c66 ("staging: erofs: fix
`erofs_workgroup_{try_to_freeze, unfreeze}'") in v5.0-rc1.
Fixed in v6.0-rc5.
Bug introduced commit was backported to following branches.
cip/4.19 cip/4.19-rt stable/4.19

Fixed status
mainline: [2f44013e39984c127c6efedf70e6b5f4e9dcf315]
stable/5.15: [8ddd001cef5e82d19192e6861068463ecca5f556]

CVE-2022-48675: IB/core: Fix a nested dead lock as part of ODP flow

Announce: https://lore.kernel.org/linux-cve-announce/2024050319-CVE-2022-48675-6ff4@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 36f30e4 ("IB/core: Improve ODP to use
hmm_range_fault()") in v5.10-rc1.
Fixed in v6.0-rc5.
Bug introduced commit is not backported to older stable kernels

Fixed status
mainline: [85eaeb5058f0f04dffb124c97c86b4f18db0b833]
stable/5.10: [e8de6cb5755eae7b793d8c00c8696c8667d44a7f]
stable/5.15: [819110054b14d7272b4188db997a3d80f75ab785]

CVE-2022-48686: nvme-tcp: fix UAF when detecting digest errors

Announce: https://lore.kernel.org/linux-cve-announce/2024050342-CVE-2022-48686-5e8e@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 3f2304f ("nvme-tcp: add NVMe over TCP host
driver") in v5.0-rc1.
Fixed in v6.0-rc5.
Bug introduced commit is not backported to older stable kernels

Fixed status
mainline: [160f3549a907a50e51a8518678ba2dcf2541abea]
stable/5.10: [5914fa32ef1b7766fea933f9eed94ac5c00aa7ff]
stable/5.15: [13c80a6c112467bab5e44d090767930555fc17a5]
stable/5.4: [19816a0214684f70b49b25075ff8c402fdd611d3]

CVE-2022-48687: ipv6: sr: fix out-of-bounds read when setting HMAC data.

Announce: https://lore.kernel.org/linux-cve-announce/2024050344-CVE-2022-48687-b82e@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 4f4853d ("ipv6: sr: implement API to control SR
HMAC structure") in v4.10-rc1.
Fixed in v6.0-rc5.
Bug introduced commit is not backported to older stable kernels

Fixed status
mainline: [84a53580c5d2138c7361c7c3eea5b31827e63b35]
stable/4.19: [f684c16971ed5e77dfa25a9ad25b5297e1f58eab]
stable/5.10: [076f2479fc5a15c4a970ca3b5e57d42ba09a31fa]
stable/5.15: [55195563ec29f80f984237b743de0e2b6ba4d093]
stable/5.4: [3df71e11a4773d775c3633c44319f7acdb89011c]

CVE-2022-48688: i40e: Fix kernel crash during module removal

Announce: https://lore.kernel.org/linux-cve-announce/2024050345-CVE-2022-48688-7306@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 0ef2d5a ("i40e: KISS the client interface") in v4.12-rc1.
Fixed in v6.0-rc5.
Bug introduced commit is not backported to older stable kernels

Fixed status
mainline: [fb8396aeda5872369a8ed6d2301e2c86e303c520]
stable/4.19: [c49f320e2492738d478bc427dcd54ccfe0cba746]
stable/5.10: [342d77769a6cceb3df7720a1e18baa4339eee3fc]
stable/5.15: [2ed94383f3a2693dbf5bc47c514b42524bd8f9ae]
stable/5.4: [5332a094514852d5e58c278cf4193adb937337fc]

CVE-2022-48689: tcp: TX zerocopy should not sense pfmemalloc status

Announce: https://lore.kernel.org/linux-cve-announce/2024050345-CVE-2022-48689-5ee7@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit c07aea3 ("mm: add a signature in struct page") in
v5.14-rc1.
Fixed in v6.0-rc5.
Bug introduced commit is not backported to older stable kernels

Fixed status
mainline: [3261400639463a853ba2b3be8bd009c2a8089775]
stable/5.15: [8527c9a6bf8e54fef0a8d3d7d8874a48c725c915]

CVE-2022-48690: ice: Fix DMA mappings leak

Announce: https://lore.kernel.org/linux-cve-announce/2024050346-CVE-2022-48690-53bc@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 617f3e1 ("ice: xsk: allocate separate memory for
XDP SW ring") in v5.16-rc7.
Fixed in v6.0-rc5.
Bug introduced commit is not backported to older stable kernels

Fixed status
mainline: [7e753eb675f0523207b184558638ee2eed6c9ac2]

CVE-2022-48691: netfilter: nf_tables: clean up hook list when offload
flags check fails

Announce: https://lore.kernel.org/linux-cve-announce/2024050346-CVE-2022-48691-5f16@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit d54725c ("netfilter: nf_tables: support for
multiple devices per netdev hook") in v5.5-rc1.
Fixed in v6.0-rc5.
Bug introduced commit is not backported to older stable kernels

Fixed status
mainline: [77972a36ecc4db7fc7c68f0e80714263c5f03f65]
stable/5.10: [910891a2a44cdc49efcc4fe7459c1085ba00d0f4]
stable/5.15: [1ce55ec5cb7c573c983dffbe290b8d17caf1f157]

CVE-2022-48692: RDMA/srp: Set scmnd->result only when scmnd is not NULL

Announce: https://lore.kernel.org/linux-cve-announce/2024050346-CVE-2022-48692-6bc3@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit ad215aa ("RDMA/srp: Make struct scsi_cmnd and
struct srp_request adjacent") in v5.14-rc1.
Fixed in v5.19.9.
Bug introduced commit was backported to following branches.
cip/5.10 cip/5.10-rt stable/5.10

Fixed status
mainline: [f2c70f56f762e5dc3b0d7dc438fbb137cb116413]
stable/5.10: [f022576aa03c2385ea7f2b27ee5b331e43abf624]
stable/5.15: [f022576aa03c2385ea7f2b27ee5b331e43abf624]

CVE-2022-48693: soc: brcmstb: pm-arm: Fix refcount leak and __iomem leak bugs

Announce: https://lore.kernel.org/linux-cve-announce/2024050347-CVE-2022-48693-3e82@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 0b741b8 ("soc: bcm: brcmstb: Add support for
S2/S3/S5 suspend states (ARM)") in v4.15-rc1.
Fixed in v6.0-rc5.
Bug introduced commit is not backported to older stable kernels

Fixed status
mainline: [1085f5080647f0c9f357c270a537869191f7f2a1]
stable/4.19: [0284b4e6dec6088a41607aa3f42bf51edff01883]
stable/5.10: [6dc0251638a4a1a998506dbd4627f8317e907558]
stable/5.15: [43245c77d9efd8c9eb91bf225d07954dcf32204d]
stable/5.4: [57b2897ec3ffe4cbe018446be6d04432919dca6b]

CVE-2022-48694: RDMA/irdma: Fix drain SQ hang with no completion

Announce: https://lore.kernel.org/linux-cve-announce/2024050347-CVE-2022-48694-f0e8@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 81091d7 ("RDMA/irdma: Add SW mechanism to
generate completions on error") in v5.19-rc1.
Fixed in v5.19.9.
Bug introduced commit was backported to following branches.
stable/5.15

Fixed status
mainline: [5becc531a3fa8da75158a8993f56cc3e0717716e]

CVE-2022-48695: scsi: mpt3sas: Fix use-after-free warning

Announce: https://lore.kernel.org/linux-cve-announce/2024050348-CVE-2022-48695-8a9e@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.0-rc5.

Fixed status
cip/4.4: [e34e499d527c3e227991fec1b3e352dc3ec047ee]
cip/4.4-rt: [e34e499d527c3e227991fec1b3e352dc3ec047ee]
cip/4.4-st: [e34e499d527c3e227991fec1b3e352dc3ec047ee]
mainline: [991df3dd5144f2e6b1c38b8d20ed3d4d21e20b34]
stable/4.19: [82efb917eeb27454dc4c6fe26432fc8f6c75bc16]
stable/5.10: [ea10a652ad2ae2cf3eced6f632a5c98f26727057]
stable/5.15: [6229fa494a5949be209bc73afbc5d0a749c2e3c7]
stable/5.4: [5682c94644fde72f72bded6580c38189ffc856b5]

CVE-2022-48696: regmap: spi: Reserve space for register address/padding

Announce: https://lore.kernel.org/linux-cve-announce/2024050348-CVE-2022-48696-b671@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit f231ff3 ("regmap: spi: Set regmap max raw r/w
from max_transfer_size") in v5.16-rc1.
Fixed in v6.0-rc5.
Bug introduced commit is not backported to older stable kernels

Fixed status
mainline: [f5723cfc01932c7a8d5c78dbf7e067e537c91439]

CVE-2022-48697: nvmet: fix a use-after-free

Announce: https://lore.kernel.org/linux-cve-announce/2024050348-CVE-2022-48697-1df4@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit a07b497 ("nvmet: add a generic NVMe target") in v4.8-rc1.
Fixed in v6.0-rc5.
Bug introduced commit is not backported to older stable kernels

Fixed status
mainline: [6a02a61e81c231cc5c680c5dbf8665275147ac52]
stable/4.19: [17f121ca3ec6be0fb32d77c7f65362934a38cc8e]
stable/5.10: [be01f1c988757b95f11f090a9f491365670a522b]
stable/5.15: [ebf46da50beb78066674354ad650606a467e33fa]
stable/5.4: [8d66989b5f7bb28bba2f8e1e2ffc8bfef4a10717]

CVE-2022-48698: drm/amd/display: fix memory leak when using debugfs_lookup()

Announce: https://lore.kernel.org/linux-cve-announce/2024050349-CVE-2022-48698-ac39@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.0-rc5.
It seems to be commit 86bc2219 ("drm/amd/display: Support crc on
specific region") in 5.13-rc1 introduced this bug.
Bug introduced commit is not backported to older stable kernels

Fixed status
mainline: [cbfac7fa491651c57926c99edeb7495c6c1aeac2]
stable/5.15: [58acd2ebae034db3bacf38708f508fbd12ae2e54]

CVE-2022-48699: sched/debug: fix dentry leak in update_sched_domain_debugfs

Announce: https://lore.kernel.org/linux-cve-announce/2024050349-CVE-2022-48699-8b9b@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.0-rc5.
It seems to be commit 3b87f136 ("sched,debug: Convert sysctl
sched_domains to debugfs") in 5.13-rc1 introduced this bug.
Bug introduced commit is not backported to older stable kernels

Fixed status
mainline: [c2e406596571659451f4b95e37ddfd5a8ef1d0dc]
stable/5.15: [26e9a1ded8923510e5529fbb28390b22228700c2]

CVE-2022-48700: vfio/type1: Unpin zero pages

Announce: https://lore.kernel.org/linux-cve-announce/2024050349-CVE-2022-48700-c756@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.0-rc5.
It seems to be commit 4b6c33b3 ("vfio/type1: Prepare for batched
pinning with struct vfio_batch") in 5.12-rc1dontuse introduced this
bug.
Bug introduced commit is not backported to older stable kernels

Fixed status
mainline: [873aefb376bbc0ed1dd2381ea1d6ec88106fdbd4]
stable/5.10: [578d644edc7d2c1ff53f7e4d0a25da473deb4a03]
stable/5.15: [5321908ef74fb593e0dbc8737d25038fc86c9986]

CVE-2022-48701: ALSA: usb-audio: Fix an out-of-bounds bug in
__snd_usb_parse_audio_interface()

Announce: https://lore.kernel.org/linux-cve-announce/2024050350-CVE-2022-48701-eadb@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.0-rc5.

Fixed status
cip/4.4: [5d45c78c420aeba3d2240644baca7a338e5d80b3]
cip/4.4-rt: [5d45c78c420aeba3d2240644baca7a338e5d80b3]
cip/4.4-st: [5d45c78c420aeba3d2240644baca7a338e5d80b3]
mainline: [e53f47f6c1a56d2af728909f1cb894da6b43d9bf]
stable/4.19: [2a308e415d247a23d4d64c964c02e782eede2936]
stable/5.10: [6123bec8480d23369e2ee0b2208611619f269faf]
stable/5.15: [98e8e67395cc6d0cdf3a771f86ea42d0ee6e59dd]
stable/5.4: [0492798bf8dfcc09c9337a1ba065da1d1ca68712]

CVE-2022-48702: ALSA: emu10k1: Fix out of bounds access in
snd_emu10k1_pcm_channel_alloc()

Announce: https://lore.kernel.org/linux-cve-announce/2024050350-CVE-2022-48702-47dd@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.0-rc5.

Fixed status
cip/4.4: [992267de945e60186027b8e9a9924a160acce5c7]
cip/4.4-rt: [992267de945e60186027b8e9a9924a160acce5c7]
cip/4.4-st: [992267de945e60186027b8e9a9924a160acce5c7]
mainline: [d29f59051d3a07b81281b2df2b8c9dfe4716067f]
stable/4.19: [88aac6684cf8bc885cca15463cb4407e91f28ff7]
stable/5.10: [39a90720f3abe96625d1224e7a7463410875de4c]
stable/5.15: [45814a53514e10a8014906c882e0d0d38df39cc1]
stable/5.4: [45321a7d02b7cf9b3f97e3987fc1e4d649b82da2]

CVE-2022-48703: thermal/int340x_thermal: handle data_vault when the
value is ZERO_SIZE_PTR

Announce: https://lore.kernel.org/linux-cve-announce/2024050351-CVE-2022-48703-3099@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.0-rc3.
It seems to be commit 0ba13c7 ("thermal/int340x_thermal: Export GDDV")
in 5.8-rc1 introduced this bug.
Bug introduced commit is not backported to older stable kernels

Fixed status
mainline: [7931e28098a4c1a2a6802510b0cbe57546d2049d]

CVE-2022-48704: drm/radeon: add a force flush to delay work when radeon

Announce: https://lore.kernel.org/linux-cve-announce/2024050351-CVE-2022-48704-e1ea@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.0-rc3.
Bug introduced commit is not backported to older stable kernels

Fixed status
cip/4.4: [e9d399fd4f22f833d6cb991feb14a8a3b0d4847d]
cip/4.4-rt: [e9d399fd4f22f833d6cb991feb14a8a3b0d4847d]
cip/4.4-st: [e9d399fd4f22f833d6cb991feb14a8a3b0d4847d]
mainline: [f461950fdc374a3ada5a63c669d997de4600dffe]
stable/4.19: [c0a45f41fde4a0f2c900f719817493ee5c4a5aa3]
stable/5.10: [826b46fd5974113515abe9e4fc8178009a8ce18c]
stable/5.15: [5a7a5b2edac4b05abd744eeaebda46d9dacd952d]
stable/5.4: [c72d97146fc5a4dff381b1737f6167e89860430d]

CVE-2022-48705: wifi: mt76: mt7921e: fix crash in chip reset fail

Announce: https://lore.kernel.org/linux-cve-announce/2024050351-CVE-2022-48705-a5c4@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 0efaf31 ("mt76: mt7921: fix MT7921E reset
failure") in v5.17-rc1.
Fixed in v6.0-rc5.
Bug introduced commit is not backported to older stable kernels

Fixed status
mainline: [fa3fbe64037839f448dc569212bafc5a495d8219]

CVE-2023-52654: io_uring/af_unix: disable sending io_uring over sockets

Announce: https://lore.kernel.org/linux-cve-announce/2024050833-CVE-2023-52654-1ae1@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 0091bfc ("io_uring/af_unix: defer registered
files gc to io_uring release") in 6.1-rc1.
Fixed in 6.7-rc5.
Bug introduced commit was backported to following branches.
cip/5.10 cip/5.10-rt stable/5.10 stable/5.15 stable/5.4 stable/6.1 stable/6.6

Fixed status
mainline: [705318a99a138c29a512a72c3e0043b3cd7f55f4]
stable/5.10: [3fe1ea5f921bf5b71cbfdc4469fb96c05936610e]
stable/5.15: [bcedd497b3b4a0be56f3adf7c7542720eced0792]
stable/5.4: [18824f592aad4124d79751bbc1500ea86ac3ff29]
stable/6.1: [f2f57f51b53be153a522300454ddb3887722fb2c]
stable/6.6: [5a33d385eb36991a91e3dddb189d8679e2aac2be]

CVE-2024-27393: xen-netfront: Add missing skb_mark_for_recycle

Announce: https://lore.kernel.org/linux-cve-announce/2024050835-CVE-2024-27393-b804@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 6c5aa6f ("xen networking: add basic XDP support
for xen-netfront") in 5.9-rc1.
Fixed in 6.9-rc3.
Bug introduced commit is not backported to older stable kernels

Fixed status
mainline: [037965402a010898d34f4e35327d22c0a95cd51f]
stable/5.15: [4143b9479caa29bb2380f3620dcbe16ea84eb3b1]
stable/6.1: [7c1250796b6c262b505a46192f4716b8c6a6a8c6]
stable/6.6: [27aa3e4b3088426b7e34584274ad45b5afaf7629]
stable/6.8: [c8b7b2f158d9d4fb89cd2f68244af154f7549bb4]

CVE-2024-27394: tcp: Fix Use-After-Free in tcp_ao_connect_init

Announce: https://lore.kernel.org/linux-cve-announce/2024050836-CVE-2024-27394-4277@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 7c2ffaf ("net/tcp: Calculate TCP-AO traffic
keys") in 6.7-rc1. Fixed in 6.9-rc6
Bug introduced commit is not backported to older stable kernels

Fixed status
mainline: [80e679b352c3ce5158f3f778cfb77eb767e586fb]
stable/6.8: [ca4fb6c6764b3f75b4f5aa81db1536291897ff7f]

CVE-2024-27395: net: openvswitch: Fix Use-After-Free in ovs_ct_exit

Announce: https://lore.kernel.org/linux-cve-announce/2024050836-CVE-2024-27395-573e@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 11efd5c ("openvswitch: Support conntrack zone
limit") in 4.18-rc1.
Fixed in 6.9-rc6.
Bug introduced commit is not backported to older stable kernels

Fixed status
mainline: [5ea7b72d4fac2fdbc0425cd8f2ea33abe95235b2]
stable/4.19: [2db9a8c0a01fa1c762c1e61a13c212c492752994]
stable/5.10: [35880c3fa6f8fe281a19975d2992644588ca33d3]
stable/5.15: [9048616553c65e750d43846f225843ed745ec0d4]
stable/5.4: [589523cf0b384164e445dd5db8d5b1bf97982424]
stable/6.1: [bca6fa2d9a9f560e6b89fd5190b05cc2f5d422c1]
stable/6.6: [eaa5e164a2110d2fb9e16c8a29e4501882235137]
stable/6.8: [edee0758747d7c219e29db9ed1d4eb33e8d32865]

CVE-2024-27396: net: gtp: Fix Use-After-Free in gtp_dellink

Announce: https://lore.kernel.org/linux-cve-announce/2024050837-CVE-2024-27396-e9af@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 94dc550 ("gtp: fix an use-after-free in
ipv4_pdp_find()") in 5.5-rc3.
Fixed in 6.9-rc6.
Bug introduced commit was backported to following branches.
cip/4.19 stable/4.19 stable/5.4

Fixed status
mainline: [f2a904107ee2b647bb7794a1a82b67740d7c8a64]
stable/4.19: [07b20d0a3dc13fb1adff10b60021a4924498da58]
stable/5.10: [0caff3e6390f840666b8dc1ecebf985c2ef3f1dd]
stable/5.15: [2e74b3fd6bf542349758f283676dff3660327c07]
stable/5.4: [718df1bc226c383dd803397d7f5d95557eb81ac7]
stable/6.1: [25a1c2d4b1fcf938356a9688a96a6456abd44b29]
stable/6.6: [2aacd4de45477582993f8a8abb9505a06426bfb6]
stable/6.8: [cd957d1716ec979d8f5bf38fc659aeb9fdaa2474]

CVE-2024-27397: netfilter: nf_tables: use timestamp to check for set
element timeout

Announce: https://lore.kernel.org/linux-cve-announce/2024050837-CVE-2024-27397-fd1e@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit c3e1b00 ("netfilter: nf_tables: add set element
timeout support") in 4.1-rc1.
Fixed in 6.8-rc4.
Bug introduced commit is not backported to older stable kernels

Fixed status
mainline: [7395dfacfff65e9938ac0889dafa1ab01e987d15]

* Updated CVEs

CVE-2023-52429: dm: limit the number of targets and parameter size area

stable/5.4 was fixed.

Fixed status
mainline: [bd504bcfec41a503b32054da5472904b404341a4]
stable/5.10: [a891a0621e725e85529985139cada8cb5a74a116]
stable/5.15: [888a0a46b80fa37eacfe81faf47ba0b83876251d]
stable/5.4: [86f4a49f32e2392c97296e89da8c25e8fb482c0d]
stable/6.1: [c5d83ac2bf6ca668a39ffb1a576899a66153ba19]
stable/6.6: [438d19492b7f002334573bae43276297eb234c80]
stable/6.7: [cd70175481f63af31901dd463e44386f033c3f4c]

CVE-2023-52614: PM / devfreq: Fix buffer overflow in trans_stat_show

stable/5.10 was fixed.

Fixed status
mainline: [08e23d05fa6dc4fc13da0ccf09defdd4bbc92ff4]
stable/5.10: [087de000e4f8c878c81d9dd3725f00a1d292980c]
stable/5.15: [796d3fad8c35ee9df9027899fb90ceaeb41b958f]
stable/6.1: [8a7729cda2dd276d7a3994638038fb89035b6f2c]
stable/6.6: [a979f56aa4b93579cf0e4265ae04d7e9300fd3e8]
stable/6.7: [eaef4650fa2050147ca25fd7ee43bc0082e03c87]

CVE-2024-23851: Kernel crash in drivers/md/dm-ioctl.c when allocate
memory more than INT_MAX bytes

stable/5.4 was fixed.

Fixed status
mainline: [bd504bcfec41a503b32054da5472904b404341a4]
stable/5.10: [a891a0621e725e85529985139cada8cb5a74a116]
stable/5.15: [888a0a46b80fa37eacfe81faf47ba0b83876251d]
stable/5.4: [86f4a49f32e2392c97296e89da8c25e8fb482c0d]
stable/6.1: [c5d83ac2bf6ca668a39ffb1a576899a66153ba19]
stable/6.6: [438d19492b7f002334573bae43276297eb234c80]
stable/6.7: [cd70175481f63af31901dd463e44386f033c3f4c]

CVE-2024-26922: drm/amdgpu: validate the parameters of bo mapping
operations more clearly

stable/4.19, stable/5.10, and stable/5.4 were fixed.

Fixed status
mainline: [6fef2d4c00b5b8561ad68dd2b68173f5c6af1e75]
stable/4.19: [d4da6b084f1c5625937d49bb6722c5b4aef11b8d]
stable/5.10: [1fd7db5c16028dc07b2ceec190f2e895dddb532d]
stable/5.15: [8b12fc7b032633539acdf7864888b0ebd49e90f2]
stable/5.4: [f68039375d4d6d67303674c0ab2d06b7295c0ec9]
stable/6.1: [212e3baccdb1939606420d88f7f52d346b49a284]
stable/6.6: [ef13eeca7c79136bc38e21eb67322c1cbd5c40ee]
stable/6.8: [b1f04b9b1c5317f562a455384c5f7473e46bdbaa]

CVE-2024-26923: af_unix: Fix garbage collector racing against connect()

stable/5.10 and stable/5.4 were fixed.

Fixed status
mainline: [47d8ac011fe1c9251070e1bd64cb10b48193ec51]
stable/5.10: [2e2a03787f4f0abc0072350654ab0ef3324d9db3]
stable/5.15: [e76c2678228f6aec74b305ae30c9374cc2f28a51]
stable/5.4: [343c5372d5e17b306db5f8f3c895539b06e3177f]
stable/6.1: [b75722be422c276b699200de90527d01c602ea7c]
stable/6.6: [507cc232ffe53a352847893f8177d276c3b532a9]
stable/6.8: [dbdf7bec5c920200077d693193f989cb1513f009]

CVE-2024-26924: netfilter: nft_set_pipapo: do not free live element

stable/5.10 was fixed.

Fixed status
mainline: [3cfc9ec039af60dbd8965ae085b2c2ccdcfbe1cc]
stable/5.10: [e3b887a9c11caf8357a821260e095f2a694a34f2]
stable/5.15: [7a1679e2d9bfa3b5f8755c2c7113e54b7d42bd46]
stable/6.1: [41d8fdf3afaff312e17466e4ab732937738d5644]
stable/6.6: [ebf7c9746f073035ee26209e38c3a1170f7b349a]
stable/6.8: [14b001ba221136c15f894577253e8db535b99487]

CVE-2024-26926: binder: check offset alignment in binder_get_object()

stable/5.10 and stable/5.4 were fixed.

Fixed status
mainline: [aaef73821a3b0194a01bd23ca77774f704a04d40]
stable/5.10: [48a1f83ca9c68518b1a783c62e6a8223144fa9fc]
stable/5.15: [a2fd6dbc98be1105a1d8e9e31575da8873ef115c]
stable/5.4: [68a28f551e4690db2b27b3db716c7395f6fada12]
stable/6.1: [a6d2a8b211c874971ee4cf3ddd167408177f6e76]
stable/6.6: [1d7f1049035b2060342f11eff957cf567d810bdc]
stable/6.8: [f01d6619045704d78613b14e2e0420bfdb7f1c15]

CVE-2024-26981: nilfs2: fix OOB in nilfs_set_de_type

cip/4.4, cip/4.4-st, stable/4.19, stable/5.10, and stable/5.4 were fixed.

Fixed status
cip/4.4: [5c5723287db65ce57c5d5b36f6d7de718051806d]
cip/4.4-st: [5c5723287db65ce57c5d5b36f6d7de718051806d]
mainline: [c4a7dc9523b59b3e73fd522c73e95e072f876b16]
stable/4.19: [054f29e9ca05be3906544c5f2a2c7321c30a4243]
stable/5.10: [7061c7efbb9e8f11ce92d6b4646405ea2b0b4de1]
stable/5.15: [bdbe483da21f852c93b22557b146bc4d989260f0]
stable/5.4: [90f43980ea6be4ad903e389be9a27a2a0018f1c8]
stable/6.1: [897ac5306bbeb83e90c437326f7044c79a17c611]
stable/6.6: [2382eae66b196c31893984a538908c3eb7506ff9]
stable/6.8: [90823f8d9ecca3d5fa6b102c8e464c62f416975f]

CVE-2024-26982: Squashfs: check the inode number is not the invalid
value of zero

stable/6.6 was fixed.

Fixed status
mainline: [9253c54e01b6505d348afbc02abaa4d9f8a01395]
stable/6.6: [be383effaee3d89034f0828038f95065b518772e]
stable/6.8: [7def00ebc9f2d6a581ddf46ce4541f84a10680e5]

CVE-2024-26984: nouveau: fix instmem race condition around ptr stores

stable/4.19, stable/5.10, and stable/5.4 were fixed.

Fixed status
mainline: [fff1386cc889d8fb4089d285f883f8cba62d82ce]
stable/4.19: [bba8ec5e9b16649d85bc9e9086bf7ae5b5716ff9]
stable/5.10: [13d76b2f443dc371842916dd8768009ff1594716]
stable/5.15: [3ab056814cd8ab84744c9a19ef51360b2271c572]
stable/5.4: [1bc4825d4c3ec6abe43cf06c3c39d664d044cbf7]
stable/6.1: [ad74d208f213c06d860916ad40f609ade8c13039]
stable/6.6: [a019b44b1bc6ed224c46fb5f88a8a10dd116e525]
stable/6.8: [21ca9539f09360fd83654f78f2c361f2f5ddcb52]

CVE-2024-26988: init/main.c: Fix potential static_command_line memory overflow

stable/5.10 was fixed.

Fixed status
mainline: [46dad3c1e57897ab9228332f03e1c14798d2d3b9]
stable/5.10: [2ef607ea103616aec0289f1b65d103d499fa903a]
stable/5.15: [0dc727a4e05400205358a22c3d01ccad2c8e1fe4]
stable/6.1: [76c2f4d426a5358fced5d5990744d46f10a4ccea]
stable/6.6: [81cf85ae4f2dd5fa3e43021782aa72c4c85558e8]
stable/6.8: [936a02b5a9630c5beb0353c3085cc49d86c57034]

CVE-2024-26993: fs: sysfs: Fix reference leak in sysfs_break_active_protection()

cip/4.4, cip/4.4-st, stable/4.19, stable/5.10, and stable/5.4 were fixed.

Fixed status
cip/4.4: [f3ae929f687a1b687dab720c39807998cdc31979]
cip/4.4-st: [f3ae929f687a1b687dab720c39807998cdc31979]
mainline: [a90bca2228c0646fc29a72689d308e5fe03e6d78]
stable/4.19: [f28bba37fe244889b81bb5c508d3f6e5c6e342c5]
stable/5.10: [84bd4c2ae9c3d0a7d3a5c032ea7efff17af17e17]
stable/5.15: [43f00210cb257bcb0387e8caeb4b46375d67f30c]
stable/5.4: [57baab0f376bec8f54b0fe6beb8f77a57c228063]
stable/6.1: [5d43e072285e81b0b63cee7189b3357c7768a43b]
stable/6.6: [ac107356aabc362aaeb77463e814fc067a5d3957]
stable/6.8: [a4c99b57d43bab45225ba92d574a8683f9edc8e4]

CVE-2024-26994: peakup: Avoid crash on very long word

cip/4.4, cip/4.4-st, stable/4.19, stable/5.10, and stable/5.4 were fixed.

Fixed status
cip/4.4: [6b94a00ec8d153f2417401c4a4abb515ec31a5f4]
cip/4.4-st: [6b94a00ec8d153f2417401c4a4abb515ec31a5f4]
mainline: [c8d2f34ea96ea3bce6ba2535f867f0d4ee3b22e1]
stable/4.19: [756c5cb7c09e537b87b5d3acafcb101b2ccf394f]
stable/5.10: [6401038acfa24cba9c28cce410b7505efadd0222]
stable/5.15: [0d130158db29f5e0b3893154908cf618896450a8]
stable/5.4: [8f6b62125befe1675446923e4171eac2c012959c]
stable/6.1: [89af25bd4b4bf6a71295f07e07a8ae7dc03c6595]
stable/6.6: [8defb1d22ba0395b81feb963b96e252b097ba76f]
stable/6.8: [0efb15c14c493263cb3a5f65f5ddfd4603d19a76]

CVE-2024-26997: usb: dwc2: host: Fix dereference issue in DDMA completion flow.

stable/4.19, stable/5.10, and stable/5.4 were fixed.

Fixed status
mainline: [eed04fa96c48790c1cce73c8a248e9d460b088f8]
stable/4.19: [257d313e37d66c3bcc87197fb5b8549129c45dfe]
stable/5.10: [26fde0ea40dda1b08fad3bc0a43f122f6dd8bddf]
stable/5.15: [8aa5c28ac65cb5e7f1b9c0c3238c00b661dd2b8c]
stable/5.4: [75bf5e78b2a27cb1bca6fa826e3ab685015165e1]
stable/6.1: [9de10b59d16880a0a3ae2876c142fe54ce45d816]
stable/6.6: [8a139fa44870e84ac228b7b76423a49610e5ba9a]
stable/6.8: [55656b2afd5f1efcec4245f3e7e814c2a9ef53f6]

CVE-2024-26999: serial/pmac_zilog: Remove flawed mitigation for rx irq flood

cip/4.4, cip/4.4-st, stable/4.19, stable/5.10, and stable/5.4 were fixed.

Fixed status
cip/4.4: [8f624cbe0eae01914b01734382b640c4bf1a9736]
cip/4.4-st: [8f624cbe0eae01914b01734382b640c4bf1a9736]
mainline: [1be3226445362bfbf461c92a5bcdb1723f2e4907]
stable/4.19: [69a02273e288011b521ee7c1f3ab2c23fda633ce]
stable/5.10: [ab86cf6f8d24e63e9aca23da5108af1aa5483928]
stable/5.15: [7a3bbe41efa55323b6ea3c35fa15941d4dbecdef]
stable/5.4: [d679c816929d62af51c8e6d7fc0e165c9412d2f3]
stable/6.1: [bbaafbb4651fede8d3c3881601ecaa4f834f9d3f]
stable/6.6: [52aaf1ff14622a04148dbb9ccce6d9de5d534ea7]
stable/6.8: [ca09dfc3cfdf89e6af3ac24e1c6c0be5c575a729]

CVE-2024-27000: serial: mxs-auart: add spinlock around changing cts state

cip/4.4, cip/4.4-st, stable/4.19, stable/5.10, stable/5.15, and
stable/5.4 were fixed.

Fixed status
cip/4.4: [4db82a6153a12db64503e59b101b6cac4b9dcffd]
cip/4.4-st: [4db82a6153a12db64503e59b101b6cac4b9dcffd]
mainline: [54c4ec5f8c471b7c1137a1f769648549c423c026]
stable/4.19: [56434e295bd446142025913bfdf1587f5e1970ad]
stable/5.10: [0dc0637e6b16158af85945425821bfd0151adb37]
stable/5.15: [479244d68f5d94f3903eced52b093c1e01ddb495]
stable/5.4: [21535ef0ac1945080198fe3e4347ea498205c99a]
stable/6.1: [2c9b943e9924cf1269e44289bc5e60e51b0f5270]
stable/6.6: [5f40fd6ca2cf0bfbc5a5c9e403dfce8ca899ba37]
stable/6.8: [94b0e65c75f4af888ab2dd6c90f060f762924e86]

CVE-2024-27001: comedi: vmk80xx: fix incomplete endpoint checking

cip/4.4, cip/4.4-st, stable/4.19, stable/5.10, and stable/5.4 were fixed.

Fixed status
cip/4.4: [677cc6c0fd70b59c6c98e2f667b0ae904a691f96]
cip/4.4-st: [677cc6c0fd70b59c6c98e2f667b0ae904a691f96]
mainline: [d1718530e3f640b7d5f0050e725216eab57a85d8]
stable/4.19: [3a63ae0348d990e137cca04eced5b08379969ea9]
stable/5.10: [f15370e315976198f338b41611f37ce82af6cf54]
stable/5.15: [b0b268eeb087e324ef3ea71f8e6cabd07630517f]
stable/5.4: [a3b8ae7e9297dd453f2977b011c5bc75eb20e71b]
stable/6.1: [ac882d6b21bffecb57bcc4486701239eef5aa67b]
stable/6.6: [59f33af9796160f851641d960bd93937f282c696]
stable/6.8: [6ec3514a7d35ad9cfab600187612c29f669069d2]

CVE-2024-27004: clk: Get runtime PM before walking tree during disable_unused

stable/5.10 and stable/5.4 were fixed.

Fixed status
mainline: [e581cf5d216289ef292d1a4036d53ce90e122469]
stable/5.10: [4af115f1a20a3d9093586079206ee37c2ac55123]
stable/5.15: [a29ec0465dce0b871003698698ac6fa92c9a5034]
stable/5.4: [253ab38d1ee652a596942156978a233970d185ba]
stable/6.1: [a424e713e0cc33d4b969cfda25b9f46df4d7b5bc]
stable/6.6: [60ff482c4205a5aac3b0595ab794cfd62295dab5]
stable/6.8: [115554862294397590088ba02f11f2aba6d5016c]

CVE-2024-27008: drm: nv04: Fix out of bounds access

cip/4.4, cip/4.4-st, stable/4.19, stable/5.10, and stable/5.4 were fixed.

Fixed status
cip/4.4: [6c19bd70caf2861a71fffd340b78ef6292a52c97]
cip/4.4-st: [6c19bd70caf2861a71fffd340b78ef6292a52c97]
mainline: [cf92bb778eda7830e79452c6917efa8474a30c1e]
stable/4.19: [c2b97f26f081ceec3298151481687071075a25cb]
stable/5.10: [097c7918fcfa1dee233acfd1f3029f00c3bc8062]
stable/5.15: [df0991da7db846f7fa4ec6740350f743d3b69b04]
stable/5.4: [5050ae879a828d752b439e3827aac126709da6d1]
stable/6.1: [5fd4b090304e450aa0e7cc9cc2b4873285c6face]
stable/6.6: [6690cc2732e2a8d0eaca44dcbac032a4b0148042]
stable/6.8: [26212da39ee14a52c76a202c6ae5153a84f579a5]

CVE-2024-27013: tun: limit printing rate when illegal packet received by tun dev

cip/4.4, cip/4.4-st, stable/4.19, stable/5.10, and stable/5.4 were fixed.

Fixed status
cip/4.4: [87478afa3b5609e994a53fcfca8b134032de52c4]
cip/4.4-st: [87478afa3b5609e994a53fcfca8b134032de52c4]
mainline: [f8bbc07ac535593139c875ffa19af924b1084540]
stable/4.19: [68459b8e3ee554ce71878af9eb69659b9462c588]
stable/5.10: [14cdb43dbc827e18ac7d5b30c5b4c676219f1421]
stable/5.15: [a50dbeca28acf7051dfa92786b85f704c75db6eb]
stable/5.4: [4b0dcae5c4797bf31c63011ed62917210d3fdac3]
stable/6.1: [62e27ef18eb4f0d33bbae8e9ef56b99696a74713]
stable/6.6: [40f4ced305c6c47487d3cd8da54676e2acc1a6ad]
stable/6.8: [52854101180beccdb9dc2077a3bea31b6ad48dfa]

CVE-2024-27020: netfilter: nf_tables: Fix potential data-race in
__nft_expr_type_get()

cip/4.4, cip/4.4-st, stable/4.19, stable/5.10, and stable/5.4 were fixed.

Fixed status
cip/4.4: [148d903916f26f7143ab04116a093708c992b81e]
cip/4.4-st: [148d903916f26f7143ab04116a093708c992b81e]
mainline: [f969eb84ce482331a991079ab7a5c4dc3b7f89bf]
stable/4.19: [939109c0a8e2a006a6cc8209e262d25065f4403a]
stable/5.10: [934e66e231cff2b18faa2c8aad0b8cec13957e05]
stable/5.15: [0b6de00206adbbfc6373b3ae38d2a6f197987907]
stable/5.4: [b38a133d37fa421c8447b383d788c9cc6f5cb34c]
stable/6.1: [8d56bad42ac4c43c6c72ddd6a654a2628bf839c5]
stable/6.6: [a9ebf340d123ae12582210407f879d6a5a1bc25b]
stable/6.8: [01f1a678b05ade4b1248019c2dcca773aebbeb7f]

CVE-2024-27022: fork: defer linking file vma until vma is fully initialized

stable/6.1 and stable/6.6 were fixed.

Fixed status
mainline: [35e351780fa9d8240dd6f7e4f245f9ea37e96c19]
stable/6.1: [0c42f7e039aba3de6d7dbf92da708e2b2ecba557]
stable/6.6: [cec11fa2eb512ebe3a459c185f4aca1d44059bbf]
stable/6.8: [abdb88dd272bbeb93efe01d8e0b7b17e24af3a34]

CVE-2023-6535: NULL pointer dereference in nvmet_tcp_execute_request

mainline, stable/5.10, stable/5.15, stable/5.4, stable/6.1, and
stable/6.6 were fixed.

Fixed status
mainline: [efa56305908ba20de2104f1b8508c6a7401833be,
0849a5441358cef02586fb2d60f707c0db195628,
  9a1abc24850eb759e36a2f8869161c3b7254c904]
stable/5.10: [f775f2621c2ac5cc3a0b3a64665dad4fb146e510,
39669fae69f302961d89f38d969c6fcc1d07eb02,
  0de2e62067d2a6733a5b8ca24066d9bbdfefaf47]
stable/5.15: [4cb3cf7177ae3666be7fb27d4ad4d72a295fb02d,
0613a2fbdf8d32c3f8f1e62d704e92251a100795,
  a300f741f692fce244e050b2cf4fe1ea3562a30f]
stable/5.4: [ee5e7632e981673f42a50ade25e71e612e543d9d,
9638beb4e10ac116c6a4fc13315e9c3608055ac0,
  40d171ef2389c46e375a428c2a13594f82849625]
stable/6.1: [2871aa407007f6f531fae181ad252486e022df42,
83ccd15717ee2b6143df72df39685f0c832e3451,
  11923a8df8edd9f85481490882a8abd50851df40]
stable/6.6: [24e05760186dc070d3db190ca61efdbce23afc88,
2f00fd8d50a7d5eedc85e62efdc1a29213168998,
  2ed3d35328901ed81baeebc3a7f4502c3dfd95f0]

Currently tracking CVEs

CVE-2021-31615: Unencrypted Bluetooth Low Energy baseband links in
Bluetooth Core Specifications 4.0 through 5.2

There is no fix information.

CVE-2020-26556: kernel: malleable commitment Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26557: kernel: predictable Authvalue in Bluetooth Mesh
Provisioning Leads to MITM

No fix information.

CVE-2020-26559: kernel: Authvalue leak in Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26560: kernel: impersonation attack in Bluetooth Mesh Provisioning

No fix information.

Regards,
-- 
Masami Ichikawa
Cybertrust Japan Co., Ltd.

Email :masami.ichikawa@cybertrust.co.jp
          :masami.ichikawa@miraclelinux.com


^ permalink raw reply	[flat|nested] 33+ messages in thread

* [kernel-cve-report] New CVE entries this week
@ 2024-05-02  3:10 Masami Ichikawa
  0 siblings, 0 replies; 33+ messages in thread
From: Masami Ichikawa @ 2024-05-02  3:10 UTC (permalink / raw)
  To: cip-dev

Hi!

It's this week's CVE report.

This week reported 207 new CVEs and 10 updated CVEs.

* New CVEs

CVE-2024-26926: binder: check offset alignment in binder_get_object()

Announce: https://lore.kernel.org/linux-cve-announce/20240424232709.718930-2-lee@kernel.org/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 6d98eb9 ("binder: avoid potential data leakage
when copying txn") in v5.17-rc1.
This commit was backported to 5.10, 5.15, and 5.4. Linux 4.x is not affected.
Fixed in v6.9-rc5.

Fixed status
mainline: [aaef73821a3b0194a01bd23ca77774f704a04d40]

CVE-2023-52646: aio: fix mremap after fork null-deref

Announce: https://lore.kernel.org/linux-cve-announce/2024042655-CVE-2023-52646-3ebb@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit e4a0d3e ("aio: Make it possible to remap aio
ring") in v3.19-rc1.
All stable kernels are fixed.
Fixed in v6.2.

Fixed status
cip/4.4: [1cb8592e28e1a99474a831820b9c8f4ba67f5e7a]
cip/4.4-rt: [1cb8592e28e1a99474a831820b9c8f4ba67f5e7a]
cip/4.4-st: [1cb8592e28e1a99474a831820b9c8f4ba67f5e7a]
mainline: [81e9d6f8647650a7bead74c5f926e29970e834d1]
stable/4.19: [d8dca1bfe9adcae38b35add64977818c0c13dd22]
stable/5.10: [c261f798f7baa8080cf0214081d43d5f86bb073f]
stable/5.15: [178993157e8c50aef7f35d7d6d3b44bb428199e1]
stable/5.4: [4326d0080f7e84fba775da41d158f46cf9d3f1c2]
stable/6.1: [af126acf01a12bdb04986fd26fc2eb3b40249e0d]

CVE-2022-48631: ext4: fix bug in extents parsing when eh_entries == 0
and eh_depth > 0

Announce: https://lore.kernel.org/linux-cve-announce/2024042851-CVE-2022-48631-cab6@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.0-rc7.
It seems as if 4.x may be affected.

Fixed status
mainline: [29a5b8a137ac8eb410cc823653a29ac0e7b7e1b0]
stable/5.10: [958b0ee23f5ac106e7cc11472b71aa2ea9a033bc]
stable/5.15: [be4df018c0be5ebecf1ca510feacc23be415cefc]
stable/5.4: [bb7eb3ca4b3b0d2c7872cf1a41c30f5e5bd65df0]

CVE-2022-48632: i2c: mlxbf: prevent stack overflow in
mlxbf_i2c_smbus_start_transaction()

Announce: https://lore.kernel.org/linux-cve-announce/2024042854-CVE-2022-48632-465f@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit b5b5b32 ("i2c: mlxbf: I2C SMBus driver for
Mellanox BlueField SoC") in v5.10-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.0-rc7.

Fixed status
mainline: [de24aceb07d426b6f1c59f33889d6a964770547b]
stable/5.10: [48ee0a864d1af02eea98fc825cc230d61517a71e]
stable/5.15: [dc2a0c587006f29b724069740c48654b9dcaebd2]

CVE-2022-48633: drm/gma500: Fix WARN_ON(lock->magic != lock) error

Announce: https://lore.kernel.org/linux-cve-announce/2024042854-CVE-2022-48633-f726@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.0-rc6.

Fixed status
mainline: [b6f25c3b94f2aadbf5cbef954db4073614943d74]

CVE-2022-48634: drm/gma500: Fix BUG: sleeping function called from
invalid context errors

Announce: https://lore.kernel.org/linux-cve-announce/2024042854-CVE-2022-48634-af99@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.0-rc6.
It looks as if commit f76c22ce ("drm/gma500: Add page flip support on
psb/cdv") in 5.6-rc1 is the first introduced commit.

Fixed status
mainline: [63e37a79f7bd939314997e29c2f5a9f0ef184281]
stable/5.10: [c5812807e416618477d1bb0049727ce8bb8292fd]
stable/5.15: [e5ae504c8623476e13032670f1a6d6344d53ec9b]

CVE-2022-48635: fsdax: Fix infinite loop in dax_iomap_rw()

Announce: https://lore.kernel.org/linux-cve-announce/2024042854-CVE-2022-48635-6286@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit ca289e0 ("fsdax: switch dax_iomap_rw to use
iomap_iter") in v5.15-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.0-rc7.

Fixed status
mainline: [17d9c15c9b9e7fb285f7ac5367dfb5f00ff575e3]
stable/5.15: [929ef155e1da41c06f4d8ca86ae12b851a83a744]

CVE-2022-48636: s390/dasd: fix Oops in dasd_alias_get_start_dev due to
missing pavgroup

Announce: https://lore.kernel.org/linux-cve-announce/2024042855-CVE-2022-48636-52a7@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 8e09f21 ("[S390] dasd: add hyper PAV support to
DASD device driver, part 1") in v2.6.25-rc1.
Fixed in v6.0-rc7.

Fixed status
mainline: [db7ba07108a48c0f95b74fabbfd5d63e924f992d]
stable/4.19: [aaba5ff2742043705bc4c02fd0b2b246e2e16da1]
stable/5.10: [f5fcc9d6d71d9ff7fdbdd4b89074e6e24fffc20b]
stable/5.15: [d3a67c21b18f33c79382084af556557c442f12a6]
stable/5.4: [2e473351400e3dd66f0b71eddcef82ee45a584c1]

CVE-2022-48637: bnxt: prevent skb UAF after handing over to PTP worker

Announce: https://lore.kernel.org/linux-cve-announce/2024042855-CVE-2022-48637-d149@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 83bb623 ("bnxt_en: Transmit and retrieve packet
timestamps") in v5.14-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.0-rc7.

Fixed status
mainline: [c31f26c8f69f776759cbbdfb38e40ea91aa0dd65]
stable/5.15: [08483e4c0c83b221b8891434a04cec405dee94a6]

CVE-2022-48638: cgroup: cgroup_get_from_id() must check the looked-up
kn is a directory

Announce: https://lore.kernel.org/linux-cve-announce/2024042855-CVE-2022-48638-e1bd@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 6b658c4 ("scsi: cgroup: Add
cgroup_get_from_id()") in v5.14-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.0-rc7.

Fixed status
mainline: [df02452f3df069a59bc9e69c84435bf115cb6e37]
stable/5.15: [8484a356cee8ce3d6a8e6266ff99be326e9273ad]

CVE-2022-48639: net: sched: fix possible refcount leak in tc_new_tfilter()

Announce: https://lore.kernel.org/linux-cve-announce/2024042855-CVE-2022-48639-be80@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 7d5509f ("net: sched: extend proto ops with 'put'
callback") in v5.1-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.0-rc7.

Fixed status
mainline: [c2e1cfefcac35e0eea229e148c8284088ce437b5]
stable/5.10: [8844c750eeb03452e2b3319c27a526f447b82596]
stable/5.15: [f8162aed962be8fa07445b2b5928e84ab40dd8d7]
stable/5.4: [903f7d322c17d8e306d766404b4604e81653902a]

CVE-2022-48640: bonding: fix NULL deref in bond_rr_gen_slave_id

Announce: https://lore.kernel.org/linux-cve-announce/2024042855-CVE-2022-48640-feee@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 848ca91 ("net: bonding: Use per-cpu
rr_tx_counter") in v5.14-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.0-rc7.

Fixed status
mainline: [0e400d602f46360752e4b32ce842dba3808e15e6]
stable/5.15: [ec3a6f4ffe556a28f6f5028bf7c4412557e7051b]

CVE-2022-48641: netfilter: ebtables: fix memory leak when blob is malformed

Announce: https://lore.kernel.org/linux-cve-announce/2024042856-CVE-2022-48641-531f@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

This bug was introduced by commit 7997eff8 ("netfilter: ebtables:
reject blobs that don't provide all entry points") in 6.0-rc3.
This commit was backported to older stable kernels except 4.4.
Fixed in 6.0-rc7.

Fixed status
mainline: [62ce44c4fff947eebdf10bb582267e686e6835c9]
stable/4.19: [1e98318af2f163eadaff815abcef38d27ca92c1e]
stable/5.10: [ebd97dbe3c55d68346b9c5fb00634a7f5b10bbee]
stable/5.15: [d5917b7af7cae0e2804f9d127a03268035098b7f]
stable/5.4: [11ebf32fde46572b0aaf3c2bdd97d923ef5a03ab]

CVE-2022-48642: netfilter: nf_tables: fix percpu memory leak at
nf_tables_addchain()

Announce: https://lore.kernel.org/linux-cve-announce/2024042856-CVE-2022-48642-b65b@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 3bc158f ("netfilter: nf_tables: map basechain
priority to hardware priority") in v5.3-rc6.
This commit is not backported to older stable kernels.
Fixed in v6.0-rc7.

Fixed status
mainline: [9a4d6dd554b86e65581ef6b6638a39ae079b17ac]
stable/5.10: [b043a525a3f5520abb676a7cd8f6328fdf959e88]
stable/5.15: [08d7524f366a886b99b1630a24a27dd6e0d7f852]

CVE-2022-48643: netfilter: nf_tables: fix nft_counters_enabled
underflow at nf_tables_addchain()

Announce: https://lore.kernel.org/linux-cve-announce/2024042856-CVE-2022-48643-7d4b@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

This bug was introduced by commit 43eb8949 ("netfilter: nf_tables: do
not leave chain stats enabled on error") in Fixed in 6.0-rc3.
This commit was backported to 5.10 and 5.15.
Fixed in 6.0-rc7.

Fixed status
mainline: [921ebde3c0d22c8cba74ce8eb3cc4626abff1ccd]
stable/5.10: [710e3f526bd23a0d33435dedc52c3144de284378]
stable/5.15: [91aa52652f4b37089aff3cb53e83049d826fef6d]

CVE-2022-48644: net/sched: taprio: avoid disabling offload when it was
never enabled

Announce: https://lore.kernel.org/linux-cve-announce/2024042856-CVE-2022-48644-757e@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 9c66d15 ("taprio: Add support for hardware
offloading") in v5.4-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.0-rc7.

Fixed status
mainline: [db46e3a88a09c5cf7e505664d01da7238cd56c92]
stable/5.10: [586def6ebed195f3594a4884f7c5334d0e1ad1bb]
stable/5.15: [f58e43184226e5e9662088ccf1389e424a3a4cbd]
stable/5.4: [d12a1eb07003e597077329767c6aa86a7e972c76]

CVE-2022-48645: net: enetc: deny offload of tc-based TSN features on
VF interfaces

Announce: https://lore.kernel.org/linux-cve-announce/2024042857-CVE-2022-48645-2325@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 34c6adf ("enetc: Configure the Time-Aware
Scheduler via tc-taprio offload") in v5.5-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.0-rc7.

Fixed status
mainline: [5641c751fe2f92d3d9e8a8e03c1263ac8caa0b42]
stable/5.15: [510e703e4ed0e011db860bc21228aff48fc9eea7]

CVE-2022-48646: sfc/siena: fix null pointer dereference in efx_hard_start_xmit

Announce: https://lore.kernel.org/linux-cve-announce/2024042857-CVE-2022-48646-35f2@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 1280479 ("sfc: decouple TXQ type from label") in v5.10-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.0-rc7.

Fixed status
mainline: [589c6eded10c77a12b7b2cf235b6b19a2bdb91fa]

CVE-2022-48647: sfc: fix TX channel offset when using legacy interrupts

Announce: https://lore.kernel.org/linux-cve-announce/2024042857-CVE-2022-48647-4a4d@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit c308dfd ("sfc: fix wrong tx channel offset with
efx_separate_tx_channels") in v5.19-rc1.
This commit was backported to 5.10 and 5.15.
Fixed in v6.0-rc7.

Fixed status
mainline: [f232af4295653afa4ade3230462b3be15ad16419]
stable/5.10: [b4afd3878f961d3517f27b3213730fceef77945c]
stable/5.15: [360910b88d1466a90644a4e0533803b594344a2b]

CVE-2022-48648: sfc: fix null pointer dereference in efx_hard_start_xmit

Announce: https://lore.kernel.org/linux-cve-announce/2024042857-CVE-2022-48648-eaf8@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 1280479 ("sfc: decouple TXQ type from label") in v5.10-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.0-rc7.

Fixed status
mainline: [0a242eb2913a4aa3d6fbdb86559f27628e9466f3]
stable/5.10: [b3b41d4d95d3822b2e459ecbc80d030ea6aec5e7]
stable/5.15: [8547c7bfc0617e7184e4da65b9b96681fcfe9998]

CVE-2022-48649: mm/slab_common: fix possible double free of kmem_cache

Announce: https://lore.kernel.org/linux-cve-announce/2024042858-CVE-2022-48649-82c3@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 0495e337b ("mm/slab_common: Deleting kobject in
kmem_cache_destroy() without holding slab_mutex/cpu_hotplug_lock") in
6.0-rc4.
This commit is not backported to older stable kernels.
Fixed in 6.0-rc7.

Fixed status
mainline: [d71608a877362becdc94191f190902fac1e64d35]

CVE-2022-48650: scsi: qla2xxx: Fix memory leak in __qlt_24xx_handle_abts()

Announce: https://lore.kernel.org/linux-cve-announce/2024042858-CVE-2022-48650-c4f0@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 8f394da ("scsi: qla2xxx: Drop
TARGET_SCF_LOOKUP_LUN_FROM_TAG") in v5.11-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.0-rc7.

Fixed status
mainline: [601be20fc6a1b762044d2398befffd6bf236cebf]
stable/5.15: [89df49e561b4a8948521fc3f8a013012eaa08f82]

CVE-2022-48651: ipvlan: Fix out-of-bound bugs caused by unset skb->mac_header

Announce: https://lore.kernel.org/linux-cve-announce/2024042858-CVE-2022-48651-ac9e@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 2ad7bf3 ("ipvlan: Initial check-in of the IPVLAN
driver.") in v3.19-rc1.
Fixed in v6.0-rc7.

Fixed status
cip/4.4: [764ab4e0a887160281881a9496f3b2704f4450a0]
cip/4.4-rt: [764ab4e0a887160281881a9496f3b2704f4450a0]
cip/4.4-st: [764ab4e0a887160281881a9496f3b2704f4450a0]
mainline: [81225b2ea161af48e093f58e8dfee6d705b16af4]
stable/4.19: [bffcdade259c05ab3436b5fab711612093c275ef]
stable/5.10: [ab4a733874ead120691e8038272d22f8444d3638]
stable/5.15: [8d06006c7eb75587d986da46c48ba9274f94e8e7]
stable/5.4: [346e94aa4a99378592c46d6a34c72703a32bd5be]

CVE-2022-48652: ice: Fix crash by keep old cfg when update TCs more than queues

Announce: https://lore.kernel.org/linux-cve-announce/2024042858-CVE-2022-48652-438f@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit a632b2a ("ice: ethtool: Prohibit improper channel
config for DCB") in v5.19-rc4.
This commit is not backported to older stable kernels.
Fixed in v6.0-rc7.

Fixed status
mainline: [a509702cac95a8b450228a037c8542f57e538e5b]

CVE-2022-48653: ice: Don't double unplug aux on peer initiated reset

Announce: https://lore.kernel.org/linux-cve-announce/2024042858-CVE-2022-48653-b6e7@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit f9f5301 ("ice: Register auxiliary device to
provide RDMA") in v5.14-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.0-rc7.

Fixed status
mainline: [23c619190318376769ad7b61504c2ea0703fb783]
stable/5.15: [34447d64b8d28e4d6a73d73f07c879959d68fbfe]

CVE-2022-48654: netfilter: nfnetlink_osf: fix possible bogus match in
nf_osf_find()

Announce: https://lore.kernel.org/linux-cve-announce/2024042859-CVE-2022-48654-e107@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 22c7652 ("netfilter: nft_osf: Add version option
support") in v5.2-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.0-rc7.

Fixed status
mainline: [559c36c5a8d730c49ef805a72b213d3bba155cc8]
stable/5.10: [5d75fef3e61e797fab5c3fbba88caa74ab92ad47]
stable/5.15: [816eab147e5c6f6621922b8515ad9010ceb1735e]
stable/5.4: [721ea8ac063d70c2078c4e762212705de6151764]

CVE-2022-48655: firmware: arm_scmi: Harden accesses to the reset domains

Announce: https://lore.kernel.org/linux-cve-announce/2024042859-CVE-2022-48655-5feb@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.0-rc7.
It looks like this bug was introduced by commit 95a15d80 ("firmware:
arm_scmi: Add RESET protocol in SCMI v2.0") in 5.4-rc1.

Fixed status
mainline: [e9076ffbcaed5da6c182b144ef9f6e24554af268]
stable/5.15: [1f08a1b26cfc53b7715abc46857c6023bb1b87de]

CVE-2022-48656: dmaengine: ti: k3-udma-private: Fix refcount leak bug
in of_xudma_dev_get()

Announce: https://lore.kernel.org/linux-cve-announce/2024042859-CVE-2022-48656-1d7a@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit d702419 ("dmaengine: ti: k3-udma: Add glue layer
for non DMAengine users") in v5.6-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.0-rc7.

Fixed status
mainline: [f9fdb0b86f087c2b7f6c6168dd0985a3c1eda87e]
stable/5.10: [aa11dae059a439af82bae541b134f8f53ac177b5]
stable/5.15: [dd5a6c5a08752b613e83ad2cb5133e72a64b876d]

CVE-2022-48657: arm64: topology: fix possible overflow in amu_fie_setup()

Announce: https://lore.kernel.org/linux-cve-announce/2024042859-CVE-2022-48657-d23e@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit cd0ed03 ("arm64: use activity monitors for
frequency invariance") in v5.7-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.0-rc7.

Fixed status
mainline: [d4955c0ad77dbc684fc716387070ac24801b8bca]
stable/5.10: [904f881b57360cf85de962d84d8614d94431f60e]
stable/5.15: [3c3edb82d67b2be9231174ac2af4af60d4af7549]

CVE-2022-48658: mm: slub: fix flush_cpu_slab()/__free_slab()
invocations in task context.

Announce: https://lore.kernel.org/linux-cve-announce/2024042800-CVE-2022-48658-4c9c@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 5a836bf ("mm: slub: move flush_cpu_slab()
invocations __free_slab() invocations out of IRQ context") in
v5.15-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.0-rc7.

Fixed status
mainline: [e45cc288724f0cfd497bb5920bcfa60caa335729]
stable/5.15: [61703b248be993eb4997b00ae5d3318e6d8f3c5b]

CVE-2022-48659: mm/slub: fix to return errno if kmalloc() fails

Announce: https://lore.kernel.org/linux-cve-announce/2024042800-CVE-2022-48659-8ccb@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 81819f0 ("SLUB core") in v2.6.22-rc1.
Fixed in v6.0-rc7.

Fixed status
cip/4.4: [e5377a5cc97a1a8d6357b42aafa06e2713930828]
cip/4.4-rt: [e5377a5cc97a1a8d6357b42aafa06e2713930828]
cip/4.4-st: [e5377a5cc97a1a8d6357b42aafa06e2713930828]
mainline: [7e9c323c52b379d261a72dc7bd38120a761a93cd]
stable/4.19: [e996821717c5cf8aa1e1abdb6b3d900a231e3755]
stable/5.10: [379ac7905ff3f0a6a4e507d3e9f710ec4fab9124]
stable/5.15: [2d6e55e0c03804e1e227b80a5746e086d6c6696c]
stable/5.4: [016b150992eebc32c4a18f783cf2bb6e2545a3d9]

CVE-2022-48660: gpiolib: cdev: Set lineevent_state::irq after IRQ
register successfully

Announce: https://lore.kernel.org/linux-cve-announce/2024042800-CVE-2022-48660-4fb8@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 4682427 ("gpiolib: cdev: refactor lineevent
cleanup into lineevent_free") in v5.9-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.0-rc7.

Fixed status
mainline: [69bef19d6b9700e96285f4b4e28691cda3dcd0d1]
stable/5.10: [657803b918e097e47d99d1489da83a603c36bcdd]
stable/5.15: [97da736cd11ae73bdf2f5e21e24446b8349e0168]

CVE-2022-48661: gpio: mockup: Fix potential resource leakage when
register a chip

Announce: https://lore.kernel.org/linux-cve-announce/2024042800-CVE-2022-48661-1b6c@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 6fda593 ("gpio: mockup: Convert to use software
nodes") in v5.15-rc6.
This commit is not backported to older stable kernels.
Fixed in v6.0-rc7.

Fixed status
mainline: [02743c4091ccfb246f5cdbbe3f44b152d5d12933]
stable/5.15: [9b26723e058faaf11b532fb4aa16d6849d581790]

CVE-2022-48662: drm/i915/gem: Really move i915_gem_context.link under
ref protection

Announce: https://lore.kernel.org/linux-cve-announce/2024042801-CVE-2022-48662-3a84@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit f8246cf ("drm/i915/gem: Drop free_work for GEM
contexts") in v5.12-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.0-rc7.

Fixed status
mainline: [d119888b09bd567e07c6b93a07f175df88857e02]
stable/5.15: [713fa3e4591f65f804bdc88e8648e219fabc9ee1]

CVE-2022-48663: gpio: mockup: fix NULL pointer dereference when removing debugfs

Announce: https://lore.kernel.org/linux-cve-announce/2024042801-CVE-2022-48663-397d@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 303e6da ("gpio: mockup: remove gpio debugfs when
remove device") in 6.0-rc4.
This commit was backported to 5.10 and 5.15.
Fixed in 6.0-rc7.

Fixed status
mainline: [b7df41a6f79dfb18ba2203f8c5f0e9c0b9b57f68]
stable/5.10: [bdea98b98f844bd8a983ca880893e509a8b4162f]
stable/5.15: [18352095a0d581f6aeb1e9fc9d68cc0152cd64b4]

CVE-2022-48664: btrfs: fix hang during unmount when stopping a space
reclaim worker

Announce: https://lore.kernel.org/linux-cve-announce/2024042801-CVE-2022-48664-d281@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit d6fd0ae ("Btrfs: fix missing delayed iputs on
unmount") in v4.20-rc2.
This commit was backported to 4.19.
Fixed in v6.0-rc7.

Fixed status
mainline: [a362bb864b8db4861977d00bd2c3222503ccc34b]
stable/5.10: [6ac5b52e3f352f9cb270c89e6e1d4dadb564ddb8]
stable/5.15: [d8a76a2e514fbbb315a6dfff2d342de2de833994]

CVE-2022-48665: exfat: fix overflow for large capacity partition

Announce: https://lore.kernel.org/linux-cve-announce/2024042801-CVE-2022-48665-527d@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 1b61383 ("exfat: reduce block requests when
zeroing a cluster") in v5.19-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.0-rc7.

Fixed status
mainline: [2e9ceb6728f1dc2fa4b5d08f37d88cbc49a20a62]

CVE-2022-48666: scsi: core: Fix a use-after-free

Announce: https://lore.kernel.org/linux-cve-announce/2024042801-CVE-2022-48666-4916@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 65ca846 ("scsi: core: Introduce
{init,exit}_cmd_priv()") in v5.7-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.0-rc5.

Fixed status
mainline: [8fe4ce5836e932f5766317cb651c1ff2a4cd0506]

CVE-2022-48667: smb3: fix temporary data corruption in insert range

Announce: https://lore.kernel.org/linux-cve-announce/2024042802-CVE-2022-48667-0aa2@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 7fe6fe9 ("cifs: add FALLOC_FL_INSERT_RANGE
support") in v5.13-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.0-rc4.

Fixed status
mainline: [9c8b7a293f50253e694f19161c045817a938e551]

CVE-2022-48668: smb3: fix temporary data corruption in collapse range

Announce: https://lore.kernel.org/linux-cve-announce/2024042802-CVE-2022-48668-3790@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 5476b5d ("cifs: add support for
FALLOC_FL_COLLAPSE_RANGE") in v5.13-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.0-rc4.

Fixed status
mainline: [fa30a81f255a56cccd89552cd6ce7ea6e8d8acc4]

CVE-2024-26927: ASoC: SOF: Add some bounds checking to firmware data

Announce: https://lore.kernel.org/linux-cve-announce/2024042844-CVE-2024-26927-3374@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit d2458ba ("ASoC: SOF: ipc3-loader: Implement
firmware parsing and loading") in v5.19-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [98f681b0f84cfc3a1d83287b77697679e0398306]
stable/6.1: [d133d67e7e724102d1e53009c4f88afaaf3e167c]
stable/6.6: [ced7df8b3c5c4751244cad79011e86cf1f809153]
stable/6.8: [9eeb8e1231f6450c574c1db979122e171a1813ab]

CVE-2024-26928: smb: client: fix potential UAF in cifs_debug_files_proc_show()

Announce: https://lore.kernel.org/linux-cve-announce/2024042849-CVE-2024-26928-e543@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.9-rc3.
It looks as if commit dfe33f9abc ("smb3: allow more detailed protocol
info on open files for debugging") in 4.20-rc1 is first introduced
commit.
This commit added cifs_debug_files_proc_show().

Fixed status
mainline: [ca545b7f0823f19db0f1148d59bc5e1a56634502]
stable/6.1: [229042314602db62559ecacba127067c22ee7b88]
stable/6.6: [a65f2b56334ba4dc30bd5ee9ce5b2691b973344d]
stable/6.8: [3402faf78b2516b0af1259baff50cc8453ef0bd1]

CVE-2022-48669: powerpc/pseries: Fix potential memleak in papr_get_attr()

Announce: https://lore.kernel.org/linux-cve-announce/2024050131-CVE-2022-48669-15cf@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 3c14b73 ("powerpc/pseries: Interface to represent
PAPR firmware attributes") in v5.18-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [cda9c0d556283e2d4adaa9960b2dc19b16156bae]
stable/6.1: [a3f22feb2220a945d1c3282e34199e8bcdc5afc4]
stable/6.6: [1699fb915b9f61794d559b55114c09a390aaf234]
stable/6.8: [d0647c3e81eff62b66d46fd4e475318cb8cb3610]

CVE-2023-52647: media: nxp: imx8-isi: Check whether crossbar pad is
non-NULL before access

Announce: https://lore.kernel.org/linux-cve-announce/2024050119-CVE-2023-52647-82e4@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit cf21f32 ("media: nxp: Add i.MX8 ISI driver") in v6.4-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [eb2f932100288dbb881eadfed02e1459c6b9504c]
stable/6.6: [c95318607fbe8fdd44991a8dad2e44118e6b8812]
stable/6.8: [91c8ce42fcde09f1da24acab9013b3e19cb88a4e]

CVE-2023-52648: drm/vmwgfx: Unmap the surface before resetting it on a
plane state

Announce: https://lore.kernel.org/linux-cve-announce/2024050122-CVE-2023-52648-4e0d@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 485d98d ("drm/vmwgfx: Add support for CursorMob
and CursorBypass 4") in v5.19-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [27571c64f1855881753e6f33c3186573afbab7ba]
stable/6.6: [0a23f95af7f28dae7c0f7c82578ca5e1a239d461]
stable/6.8: [75baad63c033b3b900d822bffbc96c9d3649bc75]

CVE-2023-52649: drm/vkms: Avoid reading beyond LUT array

Announce: https://lore.kernel.org/linux-cve-announce/2024050109-CVE-2023-52649-4614@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit db1f254 ("drm/vkms: Add support to 1D gamma LUT")
in v6.6-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [2fee84030d12d9fddfa874e4562d71761a129277]
stable/6.6: [9556c167673057d48ce4a0da675026fe046654c1]
stable/6.8: [92800aaeff51b8358d1e0a7eb74daf8aa2d7ce9d]

CVE-2023-52650: drm/tegra: dsi: Add missing check for of_find_device_by_node

Announce: https://lore.kernel.org/linux-cve-announce/2024050109-CVE-2023-52650-e2d1@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit e94236c ("drm/tegra: dsi: Add ganged mode
support") in v3.19-rc1.
Fixed in v6.9-rc1.

Fixed status
cip/4.4: [a51b1e781aff4fae622e1c1d24d6ae3391e06a97]
cip/4.4-st: [a51b1e781aff4fae622e1c1d24d6ae3391e06a97]
mainline: [afe6fcb9775882230cd29b529203eabd5d2a638d]
stable/4.19: [47a13d0b9d8527518639ab5c39667f69d6203e80]
stable/5.10: [92003981a6df5dc84af8a5904f8ee112fa324129]
stable/5.15: [93128052bf832359531c3c0a9e3567b2b8682a2d]
stable/5.4: [f05631a8525c3b5e5994ecb1304d2d878956c0f5]
stable/6.1: [50c0ad785a780c72a2fdaba10b38c645ffb4eae6]
stable/6.6: [52aa507148c4aad41436e2005d742ffcafad9976]
stable/6.8: [3169eaf1365541fd8e521091010c44fbe14691fc]

CVE-2023-52651: wifi: ath10k: fix NULL pointer dereference in
ath10k_wmi_tlv_op_pull_mgmt_tx_compl_ev()

Announce: https://lore.kernel.org/linux-cve-announce/2024050110-CVE-2023-52651-5907@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit dc40515 ("ath10k: handle mgmt tx completion
event") in v4.19-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [ad25ee36f00172f7d53242dc77c69fff7ced0755]
stable/4.19: [0cd3b0a1dc987697cba1fe93c784365aa1f8a230]
stable/5.10: [e1dc7aa814a95aeeb1b2c05be2b62af8423b15cc]
stable/5.15: [4c4e592266b6eec748ce90e82bd9cbc9838f3633]
stable/5.4: [88a9dffaec779504ab3680d33cf677741c029420]
stable/6.1: [90f089d77e38db1c48629f111f3c8c336be1bc38]
stable/6.6: [10a342fa2fe4c4dd22f2c8fe917d3b1929582076]
stable/6.8: [835c5d37f4b0ba99e9ec285ffa645bc532714191]

CVE-2023-52652: NTB: fix possible name leak in ntb_register_device()

Announce: https://lore.kernel.org/linux-cve-announce/2024050131-CVE-2023-52652-9e84@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit a1bd3ba ("NTB: Add NTB hardware abstraction
layer") in v4.2-rc1.
Fixed in v6.9-rc1.

Fixed status
mainline: [aebfdfe39b9327a3077d0df8db3beb3160c9bdd0]
stable/5.15: [a62b9f3d7bbfac874cc0c638bc1776dcf1f8ec06]
stable/6.1: [6632a54ac8057cc0b0d789c6f73883e871bcd25c]
stable/6.6: [a039690d323221eb5865f1f31db3ec264e7a14b6]
stable/6.8: [913421f9f7fd8324dcc41753d0f28b52e177ef04]

CVE-2023-52653: SUNRPC: fix a memleak in gss_import_v2_context

Announce: https://lore.kernel.org/linux-cve-announce/2024050131-CVE-2023-52653-a5c2@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 47d8480 ("gss_krb5: handle new context format
from gssd") in v2.6.35-rc1.
Fixed in v6.9-rc1.

Fixed status
mainline: [e67b652d8e8591d3b1e569dbcdfcee15993e91fa]
stable/6.6: [99044c01ed5329e73651c054d8a4baacdbb1a27c]
stable/6.8: [d111e30d9cd846bb368faf3637dc0f71fcbcf822]

CVE-2024-26929: scsi: qla2xxx: Fix double free of fcport

Announce: https://lore.kernel.org/linux-cve-announce/2024050122-CVE-2024-26929-07f0@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.9-rc2.
The qla2x00_els_dcmd_sp_free(), qla24xx_els_dcmd_iocb(), and
qla24xx_els_dcmd_iocb() were
introduced by commit 6eb54715 ("qla2xxx: Added interface to send
explicit LOGO.") in 4.5-rc1 so Linux 4.4 is not affected.
Other stable kernels might be affected.

Fixed status
mainline: [82f522ae0d97119a43da53e0f729275691b9c525]
stable/5.15: [b03e626bd6d3f0684f56ee1890d70fc9ca991c04]
stable/6.1: [282877633b25d67021a34169c5b5519b1d4ef65e]
stable/6.6: [f85af9f1aa5e2f53694a6cbe72010f754b5ff862]
stable/6.8: [846fb9f112f618ec6ae181d8dae7961652574774]

CVE-2024-26930: scsi: qla2xxx: Fix double free of the ha->vp_map pointer

Announce: https://lore.kernel.org/linux-cve-announce/2024050122-CVE-2024-26930-4f3e@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.9-rc2.
The fail_free_vp_map label was introduced by commit 430eef0 ("scsi:
qla2xxx: Relocate/rename vp map") in 6.3-rc1.

Fixed status
mainline: [e288285d47784fdcf7c81be56df7d65c6f10c58b]
stable/6.6: [f14cee7a882cb79528f17a2335f53e9fd1848467]
stable/6.8: [825d63164a2e6bacb059a9afb5605425b485413f]

CVE-2024-26931: scsi: qla2xxx: Fix command flush on cable pull

Announce: https://lore.kernel.org/linux-cve-announce/2024050123-CVE-2024-26931-01d9@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.9-rc2.

Fixed status
mainline: [a27d4d0e7de305def8a5098a614053be208d1aa1]
stable/4.19: [b73377124f56d2fec154737c2f8d2e839c237d5a]
stable/5.10: [67b2d35853c2da25a8ca1c4190a5e96d3083c2ac]
stable/5.15: [a859f6a8f4234b8ef62862bf7a92f1af5f8cd47a]
stable/5.4: [d7a68eee87b05d4e29419e6f151aef99314970a9]
stable/6.1: [09c0ac18cac206ed1218b1fe6c1a0918e5ea9211]
stable/6.6: [8de1584ec4fe0ebea33c273036e7e0a05e65c81d]
stable/6.8: [ec7587eef003cab15a13446d67c3adb88146a150]

CVE-2024-26932: usb: typec: tcpm: fix double-free issue in
tcpm_port_unregister_pd()

Announce: https://lore.kernel.org/linux-cve-announce/2024050123-CVE-2024-26932-587d@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit cd099cd ("usb: typec: tcpm: Support multiple
capabilities") in v6.8-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc2.

Fixed status
mainline: [b63f90487bdf93a4223ce7853d14717e9d452856]
stable/6.8: [242e425ed580b2f4dbcb86c8fc03a410a4084a69]

CVE-2024-26933: USB: core: Fix deadlock in port "disable" sysfs attribute

Announce: https://lore.kernel.org/linux-cve-announce/2024050123-CVE-2024-26933-c18d@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.9-rc2.
Vulnerable functions were introduced by commit f061f43d ("usb: hub:
port: add sysfs entry to switch port power") in 6.0-rc1.
This commit is not backported to older stable kernels.

Fixed status
mainline: [f4d1960764d8a70318b02f15203a1be2b2554ca1]
stable/6.1: [9dac54f08198147f5ec0ec52fcf1bc8ac899ac05]
stable/6.6: [f51849833705dea5b4f9b0c8de714dd87bd6c95c]
stable/6.8: [73d1589b91f2099e5f6534a8497b7c6b527e064e]

CVE-2024-26934: USB: core: Fix deadlock in usb_deauthorize_interface()

Announce: https://lore.kernel.org/linux-cve-announce/2024050123-CVE-2024-26934-e2fc@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 310d2b4 ("usb: interface authorization: SysFS
part of USB interface authorization") in v4.4-rc1.
Fixed in v6.9-rc2.

Fixed status
mainline: [80ba43e9f799cbdd83842fc27db667289b3150f5]
stable/4.19: [8cbdd324b41528994027128207fae8100dff094f]
stable/5.10: [e451709573f8be904a8a72d0775bf114d7c291d9]
stable/5.15: [1b175bc579f46520b11ecda443bcd2ee4904f66a]
stable/5.4: [12d6a5681a0a5cecc2af7860f0a1613fa7c6e947]
stable/6.1: [ab062fa3dc69aea88fe62162c5881ba14b50ecc5]
stable/6.6: [122a06f1068bf5e39089863f4f60b1f5d4273384]
stable/6.8: [07acf979da33c721357ff27129edf74c23c036c6]

CVE-2024-26935: scsi: core: Fix unremoved procfs host directory regression

Announce: https://lore.kernel.org/linux-cve-announce/2024050124-CVE-2024-26935-8b4e@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit be03df3 ("scsi: core: Fix a procfs host directory
removal regression") in v6.3-rc3.
This commitwas backported to 5.10, 5.15, 5.4, and 6.1. So 4.x is not affected.
Fixed in v6.9-rc2.

Fixed status
mainline: [f23a4d6e07570826fe95023ca1aa96a011fa9f84]
stable/5.10: [5c2386ba80e779a92ec3bb64ccadbedd88f779b1]
stable/5.15: [cea234bb214b17d004dfdccce4491e6ff57c96ee]
stable/5.4: [0053f15d50d50c9312d8ab9c11e2e405812dfcac]
stable/6.1: [3678cf67ff7136db1dd3bf63c361650db5d92889]
stable/6.6: [d4c34782b6d7b1e68d18d9549451b19433bd4c6c]
stable/6.8: [f4ff08fab66eb5c0b97e1a24edac052fb40bf5d7]

CVE-2024-26936: ksmbd: validate request buffer size in smb2_allocate_rsp_buf()

Announce: https://lore.kernel.org/linux-cve-announce/2024050141-CVE-2024-26936-0264@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.9-rc6.
The ksmbd was introduced in 5.10 so prior to 5.15 kernels aren't affected.

Fixed status
mainline: [17cf0c2794bdb6f39671265aa18aea5c22ee8c4a]
stable/6.1: [21ff9d7d223c5c19cb4334009e4c0c83a2f4d674]
stable/6.6: [5c20b242d4fed73a93591e48bfd9772e2322fb11]
stable/6.8: [2c27a64a2bc47d9bfc7c3cf8be14be53b1ee7cb6]

CVE-2024-26937: drm/i915/gt: Reset queue_priority_hint on parking

Announce: https://lore.kernel.org/linux-cve-announce/2024050124-CVE-2024-26937-3d21@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 22b7a42 ("drm/i915/execlists: Preempt-to-busy")
in v5.4-rc1.
Thic commit is not backported to older stable kernels.
Fixed in v6.9-rc2.

Fixed status
mainline: [4a3859ea5240365d21f6053ee219bb240d520895]
stable/5.10: [fe34587acc995e7b1d7a5d3444a0736721ec32b3]
stable/5.15: [ac9b6b3e8d1237136c8ebf0fa1ce037dd7e2948f]
stable/5.4: [67944e6db656bf1e986aa2a359f866f851091f8a]
stable/6.1: [7eab7b021835ae422c38b968d5cc60e99408fb62]
stable/6.6: [3b031e4fcb2740988143c303f81f69f18ce86325]
stable/6.8: [8fd9b0ce8c26533fe4d5d15ea15bbf7b904b611c]

CVE-2024-26938: drm/i915/bios: Tolerate devdata==NULL in
intel_bios_encoder_supports_dp_dual_mode()

Announce: https://lore.kernel.org/linux-cve-announce/2024050124-CVE-2024-26938-b3f9@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.9-rc2.
It seems to be commit 044cbc7 ("drm/i915/bios: Nuke
DEVICE_TYPE_DP_DUAL_MODE_BITS") in 5.18-rc1 is suspicious.

Fixed status
mainline: [32e39bab59934bfd3f37097d4dd85ac5eb0fd549]
stable/6.1: [72e4d3fb72e9f0f016946158a7d95304832768e6]
stable/6.6: [a891add409e3bc381f4f68c2ce9d953f1865cb1f]
stable/6.8: [94cf2fb6feccd625e5b4e23e1b70f39a206f82ac]

CVE-2024-26939: drm/i915/vma: Fix UAF on destroy against retire race

Announce: https://lore.kernel.org/linux-cve-announce/2024050124-CVE-2024-26939-5314@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit d939397 ("drm/i915: Remove the vma refcount") in v5.19-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc2.

Fixed status
mainline: [0e45882ca829b26b915162e8e86dbb1095768e9e]
stable/6.1: [704edc9252f4988ae1ad7dafa23d0db8d90d7190]
stable/6.6: [5e3eb862df9f972ab677fb19e0d4b9b1be8db7b5]
stable/6.8: [59b2626dd8c8a2e13f18054b3530e0c00073d79f]

CVE-2024-26940: drm/vmwgfx: Create debugfs ttm_resource_manager entry
only if needed

Announce: https://lore.kernel.org/linux-cve-announce/2024050125-CVE-2024-26940-1785@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit af4a25b ("drm/vmwgfx: Add debugfs entries for
various ttm resource managers") in v5.19-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc2.

Fixed status
mainline: [4be9075fec0a639384ed19975634b662bfab938f]
stable/6.1: [016119154981d81c9e8f2ea3f56b9e2b4ea14500]
stable/6.6: [042ef0afc40fa1a22b3608f22915b91ce39d128f]
stable/6.8: [eb08db0fc5354fa17b7ed66dab3c503332423451]

CVE-2024-26941: drm/dp: Fix divide-by-zero regression on DP MST unplug
with nouveau

Announce: https://lore.kernel.org/linux-cve-announce/2024050125-CVE-2024-26941-7c68@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit c1d6a22 ("drm/dp: Add helpers to calculate the
link BW overhead") in v6.8-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc2.

Fixed status
mainline: [9cbd1dae842737bfafa4b10a87909fa209dde250]
stable/6.8: [828862071a6ca0c52655e6e62ac7abfef3e5c578]

CVE-2024-26942: net: phy: qcom: at803x: fix kernel panic with at8031_probe

Announce: https://lore.kernel.org/linux-cve-announce/2024050125-CVE-2024-26942-2f72@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 25d2ba9 ("net: phy: at803x: move specific at8031
probe mode check to dedicated probe") in v6.8-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc2.

Fixed status
mainline: [6a4aee277740d04ac0fd54cfa17cc28261932ddc]
stable/6.8: [a8a296ad9957b845b89bcf48be1cf8c74875ecc3]

CVE-2024-26943: nouveau/dmem: handle kcalloc() allocation failure

Announce: https://lore.kernel.org/linux-cve-announce/2024050125-CVE-2024-26943-9ea5@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 2498812 ("nouveau/dmem: evict device private
memory during release") in v6.1-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc2.

Fixed status
mainline: [16e87fe23d4af6df920406494ced5c0f4354567b]
stable/6.1: [9acfd8b083a0ffbd387566800d89f55058a68af2]
stable/6.6: [2a84744a037b8a511d6a9055f3defddc28ff4a4d]
stable/6.8: [3e82f7383e0b82a835e6b6b06a348b2bc4e2c2ee]

CVE-2024-26944: btrfs: zoned: fix use-after-free in do_zone_finish()

Announce: https://lore.kernel.org/linux-cve-announce/2024050125-CVE-2024-26944-598c@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.9-rc2.

Fixed status
mainline: [1ec17ef59168a1a6f1105f5dc517f783839a5302]
stable/6.8: [34ca809e055eca5cfe63d9c7efbf80b7c21b4e57]

CVE-2024-26945: crypto: iaa - Fix nr_cpus < nr_iaa case

Announce: https://lore.kernel.org/linux-cve-announce/2024050126-CVE-2024-26945-bf47@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.9-rc2.
It looks as if commit f57bf3f7 ("crypto: iaa - Add per-cpu workqueue
table with rebalancing") in 6.8-rc1 introduced this bug.

Fixed status
mainline: [5a7e89d3315d1be86aff8a8bf849023cda6547f7]
stable/6.8: [a5ca1be7f9817de4e93085778b3ee2219bdc2664]

CVE-2024-26946: kprobes/x86: Use copy_from_kernel_nofault() to read
from unsafe address

Announce: https://lore.kernel.org/linux-cve-announce/2024050126-CVE-2024-26946-ad5d@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit cc66bb9 ("x86/ibt,kprobes: Cure sym+0 equals
fentry woes") in v5.18-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [4e51653d5d871f40f1bd5cf95cc7f2d8b33d063b]
stable/6.1: [6417684315087904fffe8966d27ca74398c57dd6]
stable/6.6: [f13edd1871d4fb4ab829aff629d47914e251bae3]
stable/6.8: [b69f577308f1070004cafac106dd1a44099e5483]

CVE-2024-26947: ARM: 9359/1: flush: check if the folio is reserved for
no-mapping addresses

Announce: https://lore.kernel.org/linux-cve-announce/2024050126-CVE-2024-26947-c9b8@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit a4d5613 ("arm: extend pfn_valid to take into
account freed memory map alignment") in v5.14-rc1.
This commit was backported to 5.10 and 5.4. Linux 4.x is not affected.
Fixed in v6.9-rc1.

Fixed status
mainline: [0c66c6f4e21cb22220cbd8821c5c73fc157d20dc]
stable/6.6: [0c027c2bad7f5111c51a358b5d392e1a695dabff]
stable/6.8: [fb3a122a978626b33de3367ee1762da934c0f512]

CVE-2024-26948: drm/amd/display: Add a dc_state NULL check in dc_state_release

Announce: https://lore.kernel.org/linux-cve-announce/2024050126-CVE-2024-26948-43bb@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.9-rc1.
It looks as if commit 09a4ec5da ("drm/amd/display: Refactor dc_state
interface") in 6.8-rc1 was introduced this bug.

Fixed status
mainline: [334b56cea5d9df5989be6cf1a5898114fa70ad98]
stable/6.8: [d37a08f840485995e3fb91dad95e441b9d28a269]

CVE-2024-26949: drm/amdgpu/pm: Fix NULL pointer dereference when get power limit

Announce: https://lore.kernel.org/linux-cve-announce/2024050127-CVE-2024-26949-cf74@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 7968e97 ("drm/amdgpu/pm: Fix the power1_min_cap
value") in v6.8-rc7.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [08ae9ef829b8055c2fdc8cfee37510c1f4721a07]
stable/6.8: [b8eaa8ef1f1157a9f330e36e66bdd7a693309948]

CVE-2024-26950: wireguard: netlink: access device through ctx instead of peer

Announce: https://lore.kernel.org/linux-cve-announce/2024050127-CVE-2024-26950-4424@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit e7096c1 ("net: WireGuard secure network tunnel")
in v5.6-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [71cbd32e3db82ea4a74e3ef9aeeaa6971969c86f]
stable/5.10: [493aa6bdcffd90a4f82aa614fe4f4db0641b4068]
stable/5.15: [4be453271a882c8ebc28df3dbf9e4d95e6ac42f5]
stable/6.1: [09c3fa70f65175861ca948cb2f0f791e666c90e5]
stable/6.6: [c991567e6c638079304cc15dff28748e4a3c4a37]
stable/6.8: [d44bd323d8bb8031eef4bdc44547925998a11e47]

CVE-2024-26951: wireguard: netlink: check for dangling peer via
is_dead instead of empty list

Announce: https://lore.kernel.org/linux-cve-announce/2024050127-CVE-2024-26951-5cbe@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit e7096c1 ("net: WireGuard secure network tunnel")
in v5.6-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [55b6c738673871c9b0edae05d0c97995c1ff08c4]
stable/5.10: [f52be46e3e6ecefc2539119784324f0cbc09620a]
stable/5.15: [710a177f347282eea162aec8712beb1f42d5ad87]
stable/6.1: [b7cea3a9af0853fdbb1b16633a458f991dde6aac]
stable/6.6: [13d107794304306164481d31ce33f8fdb25a9c04]
stable/6.8: [302b2dfc013baca3dea7ceda383930d9297d231d]

CVE-2024-26952: ksmbd: fix potencial out-of-bounds when buffer offset is invalid

Announce: https://lore.kernel.org/linux-cve-announce/2024050127-CVE-2024-26952-7f65@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.9-rc1.
It looks as if this bug was introduced by commit e2f34481b ("cifsd:
add server-side procedures for SMB3") in 5.15-rc1.

Fixed status
mainline: [c6cd2e8d2d9aa7ee35b1fa6a668e32a22a9753da]
stable/6.8: [0c5541b4c980626fa3cab16ba1a451757778bbb5]

CVE-2024-26953: net: esp: fix bad handling of pages from page_pool

Announce: https://lore.kernel.org/linux-cve-announce/2024050128-CVE-2024-26953-8304@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 6a5bcd8 ("page_pool: Allow drivers to hint on SKB
recycling") in v5.14-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [c3198822c6cb9fb588e446540485669cc81c5d34]
stable/6.6: [8291b4eac429c480386669444c6377573f5d8664]
stable/6.8: [f278ff9db67264715d0d50e3e75044f8b78990f4]

CVE-2024-26954: ksmbd: fix slab-out-of-bounds in smb_strndup_from_utf16()

Announce: https://lore.kernel.org/linux-cve-announce/2024050128-CVE-2024-26954-18d5@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.9-rc1.
It looks as if commit d10c7787 ("ksmbd: fix slab-out-of-bounds in
smb_strndup_from_utf16()") in 6.7-rc8 introduced this bug.
This commit was backported to 5.15, 6.1, and 6.6.

Fixed status
mainline: [a80a486d72e20bd12c335bcd38b6e6f19356b0aa]
stable/6.8: [4f97e6a9d62cb1fce82fbf4baff44b83221bc178]

CVE-2024-26955: nilfs2: prevent kernel bug at submit_bh_wbc()

Announce: https://lore.kernel.org/linux-cve-announce/2024050128-CVE-2024-26955-3205@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 1f5abe7 ("nilfs2: replace BUG_ON and BUG calls
triggerable from ioctl") in v2.6.30-rc1.
Fixed in v6.9-rc1.

Fixed status
cip/4.4: [000f2bf0e2d314ae3c76a4f8f845b3056d6374ca]
cip/4.4-st: [000f2bf0e2d314ae3c76a4f8f845b3056d6374ca]
mainline: [269cdf353b5bdd15f1a079671b0f889113865f20]
stable/4.19: [91e4c4595fae5e87069e44687ae879091783c183]
stable/5.10: [f0fe7ad5aff4f0fcf988913313c497de85f1e186]
stable/5.15: [ca581d237f3b8539c044205bb003de71d75d227c]
stable/5.4: [32eaee72e96590a75445c8a6c7c1057673b47e07]
stable/6.1: [192e9f9078c96be30b31c4b44d6294b24520fce5]
stable/6.6: [0c8aa4cfda4e4adb15d5b6536d155eca9c9cd44c]
stable/6.8: [76ffbe911e2798c7296968f5fd72f7bf67207a8d]

CVE-2024-26956: nilfs2: fix failure to detect DAT corruption in btree
and direct mappings

Announce: https://lore.kernel.org/linux-cve-announce/2024050128-CVE-2024-26956-94b7@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit c3a7abf ("nilfs2: support contiguous lookup of
blocks") in v2.6.31-rc1.
Fixed in v6.9-rc1.

Fixed status
cip/4.4: [bde10c01a7966debaaba115700bc3de40d3d40ef]
cip/4.4-st: [bde10c01a7966debaaba115700bc3de40d3d40ef]
mainline: [f2f26b4a84a0ef41791bd2d70861c8eac748f4ba]
stable/4.19: [b67189690eb4b7ecc84ae16fa1e880e0123eaa35]
stable/5.10: [c3b5c5c31e723b568f83d8cafab8629d9d830ffb]
stable/5.15: [2e2619ff5d0def4bb6c2037a32a6eaa28dd95c84]
stable/5.4: [9cbe1ad5f4354f4df1445e5f4883983328cd6d8e]
stable/6.1: [46b832e09d43b394ac0f6d9485d2b1a06593f0b7]
stable/6.6: [f69e81396aea66304d214f175aa371f1b5578862]
stable/6.8: [82827ca21e7c8a91384c5baa656f78a5adfa4ab4]

CVE-2024-26957: s390/zcrypt: fix reference counting on zcrypt card objects

Announce: https://lore.kernel.org/linux-cve-announce/2024050129-CVE-2024-26957-9e6b@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.9-rc1.
The zcrypt_pick_queue() was introduced by commit e28d2af
("s390/zcrypt: add multi domain support") in 4.10-rc1.

Fixed status
mainline: [50ed48c80fecbe17218afed4f8bed005c802976c]
stable/4.19: [7e500849fa558879a1cde43f80c7c048c2437058]
stable/5.10: [6470078ab3d8f222115e11c4ec67351f3031b3dd]
stable/5.15: [a55677878b93e9ebc31f66d0e2fb93be5e7836a6]
stable/5.4: [9daddee03de3f231012014dab8ab2b277a116a55]
stable/6.1: [b7f6c3630eb3f103115ab0d7613588064f665d0d]
stable/6.6: [a64ab862e84e3e698cd351a87cdb504c7fc575ca]
stable/6.8: [394b6d8bbdf9ddee6d5bcf3e1f3e9f23eecd6484]

CVE-2024-26958: nfs: fix UAF in direct writes

Announce: https://lore.kernel.org/linux-cve-announce/2024050129-CVE-2024-26958-6c15@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.9-rc1.
It looks all stable kernels are affected. However, nfs_commit_begin()
and nfs_commit_end() are introduced
by commit af7cf0579 ("NFS: Allow multiple commit requests in flight
per file") in 4.5-rc1.
So, backporting this fix to 4.4 also needs backport commit af7cf0579 too.

Fixed status
mainline: [17f46b803d4f23c66cacce81db35fef3adb8f2af]
stable/5.10: [4595d90b5d2ea5fa4d318d13f59055aa4bf3e7f5]
stable/5.15: [80d24b308b7ee7037fc90d8ac99f6f78df0a256f]
stable/6.1: [3abc2d160ed8213948b147295d77d44a22c88fa3]
stable/6.6: [e25447c35f8745337ea8bc0c9697fcac14df8605]
stable/6.8: [cf54f66e1dd78990ec6b32177bca7e6ea2144a95]

CVE-2024-26959: Bluetooth: btnxpuart: Fix btnxpuart_close

Announce: https://lore.kernel.org/linux-cve-announce/2024050129-CVE-2024-26959-cbbc@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 689ca16 ("Bluetooth: NXP: Add protocol support
for NXP Bluetooth chipsets") in v6.4-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [664130c0b0309b360bc5bdd40a30604a9387bde8]
stable/6.6: [d4e2365b07f1ae1f811a915b514caef5b2d6581e]
stable/6.8: [74bcf708775c405f7fb6ed776ccd3e1957f38a52]

CVE-2024-26960: mm: swap: fix race between free_swap_and_cache() and swapoff()

Announce: https://lore.kernel.org/linux-cve-announce/2024050129-CVE-2024-26960-ad6b@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 7c00baf ("mm/swap: free swap slots in batch") in v4.11-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [82b1c07a0af603e3c47b906c8e991dc96f01688e]
stable/5.10: [d85c11c97ecf92d47a4b29e3faca714dc1f18d0d]
stable/5.15: [2da5568ee222ce0541bfe446a07998f92ed1643e]
stable/6.1: [1ede7f1d7eed1738d1b9333fd1e152ccb450b86a]
stable/6.6: [0f98f6d2fb5fad00f8299b84b85b6bc1b6d7d19a]
stable/6.8: [363d17e7f7907c8e27a9e86968af0eaa2301787b]

CVE-2024-26961: mac802154: fix llsec key resources release in
mac802154_llsec_key_del

Announce: https://lore.kernel.org/linux-cve-announce/2024050129-CVE-2024-26961-408d@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 5d637d5 ("mac802154: add llsec structures and
mutators") in v3.16-rc1.
Fixed in v6.9-rc1.

Fixed status
mainline: [e8a1e58345cf40b7b272e08ac7b32328b2543e40]
stable/5.10: [068ab2759bc0b4daf0b964de61b2731449c86531]
stable/5.15: [d3d858650933d44ac12c1f31337e7110c2071821]
stable/6.1: [dcd51ab42b7a0431575689c5f74b8b6efd45fc2f]
stable/6.6: [20d3e1c8a1847497269f04d874b2a5818ec29e2d]
stable/6.8: [49c8951680d7b76fceaee89dcfbab1363fb24fd1]

CVE-2024-26962: dm-raid456, md/raid456: fix a deadlock for dm-raid456
while io concurrent with reshape

Announce: https://lore.kernel.org/linux-cve-announce/2024050130-CVE-2024-26962-cbb0@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.9-rc1.
It seems as if commit c467e97 (" md/raid6: use valid sector values to
determine if an I/O should wait on the reshape") in 6.7-rc5 introduced
this bug.
This commit was backported to 6.1 and 6.8.

Fixed status
mainline: [41425f96d7aa59bc865f60f5dda3d7697b555677]
stable/6.8: [a8d249d770cb357d16a2097b548d2e4c1c137304]

CVE-2024-26963: usb: dwc3-am62: fix module unload/reload behavior

Announce: https://lore.kernel.org/linux-cve-announce/2024050130-CVE-2024-26963-3eac@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit e8784c0 ("drivers: usb: dwc3: Add AM62 USB
wrapper driver") in v5.19-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [6661befe41009c210efa2c1bcd16a5cc4cff8a06]
stable/6.1: [6c6a45645a2e6a272dfde14eddbb6706de63c25d]
stable/6.6: [7dfed9855397d0df4c6f748d1f66547ab3bad766]
stable/6.8: [3895780fabd120d0fbd54354014e85207b25687c]

CVE-2024-26964: usb: xhci: Add error handling in xhci_map_urb_for_dma

Announce: https://lore.kernel.org/linux-cve-announce/2024050130-CVE-2024-26964-54c8@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 2017a1e ("usb: xhci: Use temporary buffer to
consolidate SG") in v5.11-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [be95cc6d71dfd0cba66e3621c65413321b398052]
stable/5.15: [4a49d24fdec0a802aa686a567a3989a9fdf4e5dd]
stable/6.1: [b2c898469dfc388f619c6c972a28466cbb1442ea]
stable/6.6: [620b6cf2f1a270f48d38e6b8ce199c1acb3e90f4]
stable/6.8: [7b6cc33593d7ccfc3011b290849cfa899db46757]

CVE-2024-26965: clk: qcom: mmcc-msm8974: fix terminating of frequency
table arrays

Announce: https://lore.kernel.org/linux-cve-announce/2024050130-CVE-2024-26965-a43f@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit d8b2120 ("clk: qcom: Add support for MSM8974's
multimedia clock controller (MMCC)") in v3.14-rc1.
Fixed in v6.9-rc1.

Fixed status
cip/4.4: [3cca1982cbcd70f6656e47339e497041d62f8322]
cip/4.4-st: [3cca1982cbcd70f6656e47339e497041d62f8322]
mainline: [e2c02a85bf53ae86d79b5fccf0a75ac0b78e0c96]
stable/4.19: [99740c4791dc8019b0d758c5389ca6d1c0604d95]
stable/5.10: [3ff4a0f6a8f0ad4b4ee9e908bdfc3cacb7be4060]
stable/5.15: [8f562f3b25177c2055b20fd8cf000496f6fa9194]
stable/5.4: [86bf75d9158f511db7530bc82a84b19a5134d089]
stable/6.1: [537040c257ab4cd0673fbae048f3940c8ea2e589]
stable/6.6: [7e9926fef71e514b4a8ea9d11d5a84d52b181362]
stable/6.8: [ca2cf98d46748373e830a13d85d215d64a2d9bf2]

CVE-2024-26966: clk: qcom: mmcc-apq8084: fix terminating of frequency
table arrays

Announce: https://lore.kernel.org/linux-cve-announce/2024050131-CVE-2024-26966-1afc@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 2b46cd2 ("clk: qcom: Add APQ8084 Multimedia Clock
Controller (MMCC) support") in v3.17-rc1.
Fixed in v6.9-rc1.

Fixed status
cip/4.4: [b112d88ea7c5551b113e4712f42815a94fcac58c]
cip/4.4-st: [b112d88ea7c5551b113e4712f42815a94fcac58c]
mainline: [a903cfd38d8dee7e754fb89fd1bebed99e28003d]
stable/4.19: [5533686e99b04994d7c4877dc0e4282adc9444a2]
stable/5.10: [a09aecb6cb482de88301c43bf00a6c8726c4d34f]
stable/5.15: [3aedcf3755c74dafc187eb76acb04e3e6348b1a9]
stable/5.4: [b2dfb216f32627c2f6a8041f2d9d56d102ab87c0]
stable/6.1: [185de0b7cdeaad8b89ebd4c8a258ff2f21adba99]
stable/6.6: [9b4c4546dd61950e80ffdca1bf6925f42b665b03]
stable/6.8: [5638330150db2cc30b53eed04e481062faa3ece8]

CVE-2024-26967: clk: qcom: camcc-sc8280xp: fix terminating of
frequency table arrays

Announce: https://lore.kernel.org/linux-cve-announce/2024050131-CVE-2024-26967-3ccc@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit ff93872 ("clk: qcom: camcc-sc8280xp: Add sc8280xp
CAMCC") in v6.8-rc1.
Fixed in v6.9-rc1.

Fixed status
mainline: [6a3d70f7802a98e6c28a74f997a264118b9f50cd]
stable/6.8: [93ff48729211dae55df5d216023be4528d29babb]

CVE-2024-26968: clk: qcom: gcc-ipq9574: fix terminating of frequency
table arrays

Announce: https://lore.kernel.org/linux-cve-announce/2024050131-CVE-2024-26968-bd35@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit d75b82c ("clk: qcom: Add Global Clock Controller
driver for IPQ9574") in v6.4-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [bd2b6395671d823caa38d8e4d752de2448ae61e1]
stable/6.6: [0204247cf3669b6021fb745c3b7f37ae392ab19c]
stable/6.8: [604f2d7c46727c5e24fc7faddc980bc1cc0b1011]

CVE-2024-26969: clk: qcom: gcc-ipq8074: fix terminating of frequency
table arrays

Announce: https://lore.kernel.org/linux-cve-announce/2024050131-CVE-2024-26969-13cf@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 9607f62 ("clk: qcom: ipq8074: add PCIE, USB and
SDCC clocks") in v4.16-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [1040ef5ed95d6fd2628bad387d78a61633e09429]
stable/4.19: [e117c6e2d1617520f5f7d7f6f6b395f01d8b5a27]
stable/5.10: [851cc19bdb02556fb13629b3e4fef6f2bdb038fe]
stable/5.15: [9de184d4e557d550fb0b7b833b676bda4f269e4f]
stable/5.4: [83fe1bbd9e259ad109827ccfbfc2488e0dea8e94]
stable/6.1: [dd92b159c506804ac57adf3742d9728298bb1255]
stable/6.6: [b6b31b4c67ea6bd9222e5b73b330554c57f2f90d]
stable/6.8: [be9e2752d823eca1d5af67014a1844a9176ff566]

CVE-2024-26970: clk: qcom: gcc-ipq6018: fix terminating of frequency
table arrays

Announce: https://lore.kernel.org/linux-cve-announce/2024050132-CVE-2024-26970-ad9a@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit d9db07f ("clk: qcom: Add ipq6018 Global Clock
Controller support") in v5.6-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [cdbc6e2d8108bc47895e5a901cfcaf799b00ca8d]
stable/5.10: [ae60e3342296f766f88911d39199f77b05f657a6]
stable/5.15: [b4527ee3de365a742215773d20f07db3e2c06f3b]
stable/6.1: [852db52b45ea96dac2720f108e7c7331cd3738bb]
stable/6.6: [421b135aceace99789c982f6a77ce9476564fb52]
stable/6.8: [db4066e3ab6b3d918ae2b92734a89c04fe82cc1d]

CVE-2024-26971: clk: qcom: gcc-ipq5018: fix terminating of frequency
table arrays

Announce: https://lore.kernel.org/linux-cve-announce/2024050132-CVE-2024-26971-6e28@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit e3fdbef ("clk: qcom: Add Global Clock controller
(GCC) driver for IPQ5018") in v6.6-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [90ad946fff70f312b8d23226afc38c13ddd88c4b]
stable/6.6: [b0cf3d200e8a72b6d28e6e088c062b4a98cb5eaf]
stable/6.8: [50c3acd460551cdf9d8ac6fe0c04f2de0e8e0872]

CVE-2024-26972: ubifs: ubifs_symlink: Fix memleak of inode->i_link in error path

Announce: https://lore.kernel.org/linux-cve-announce/2024050132-CVE-2024-26972-bf6c@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 2c58d54 ("fscrypt: cache decrypted symlink target
in ->i_link") in v5.2-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [6379b44cdcd67f5f5d986b73953e99700591edfa]
stable/6.8: [62b5ae00c2b835639002ce898ccb5d82c51073ae]

CVE-2024-26973: fat: fix uninitialized field in nostale filehandles

Announce: https://lore.kernel.org/linux-cve-announce/2024050132-CVE-2024-26973-54a3@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit ea3983a ("fat: restructure export_operations") in
v3.10-rc1.
Fixed in v6.9-rc1.

Fixed status
cip/4.4: [3dee18ecb83d8f2881438721a9f519a07fabe35f]
cip/4.4-st: [3dee18ecb83d8f2881438721a9f519a07fabe35f]
mainline: [fde2497d2bc3a063d8af88b258dbadc86bd7b57c]
stable/4.19: [9840d1897e28f8733cc1e38f97e044f987dc0a63]
stable/5.10: [a276c595c3a629170b0f052a3724f755d7c6adc6]
stable/5.15: [b7fb63e807c6dadf7ecc1d43448c4f1711d7eeee]
stable/5.4: [f52d7663a10a1266a2d3871a6dd8fd111edc549f]
stable/6.1: [c8cc05de8e6b5612b6e9f92c385c1a064b0db375]
stable/6.6: [03a7e3f2ba3ca25f1da1d3898709a08db14c1abb]
stable/6.8: [cdd33d54e789d229d6d5007cbf3f53965ca1a5c6]

CVE-2024-26974: crypto: qat - resolve race condition during AER recovery

Announce: https://lore.kernel.org/linux-cve-announce/2024050132-CVE-2024-26974-13eb@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit d8cba25 ("crypto: qat - Intel(R) QAT driver
framework") in v3.17-rc1.
Fixed in v6.9-rc1.

Fixed status
cip/4.4: [e30f053113cfc576201b3b666d9258466e692ffb]
cip/4.4-st: [e30f053113cfc576201b3b666d9258466e692ffb]
mainline: [7d42e097607c4d246d99225bf2b195b6167a210c]
stable/4.19: [daba62d9eeddcc5b1081be7d348ca836c83c59d7]
stable/5.10: [d03092550f526a79cf1ade7f0dfa74906f39eb71]
stable/5.15: [4ae5a97781ce7d6ecc9c7055396535815b64ca4f]
stable/5.4: [8e81cd58aee14a470891733181a47d123193ba81]
stable/6.1: [226fc408c5fcd23cc4186f05ea3a09a7a9aef2f7]
stable/6.6: [8a5a7611ccc7b1fba8d933a9f22a2e76859d94dc]
stable/6.8: [bb279ead42263e9fb09480f02a4247b2c287d828]

CVE-2024-26975: powercap: intel_rapl: Fix a NULL pointer dereference

Announce: https://lore.kernel.org/linux-cve-announce/2024050133-CVE-2024-26975-d184@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 1488ac9 ("powercap: intel_rapl: Allow probing
without CPUID match") in v6.5-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [2d1f5006ff95770da502f8cee2a224a1ff83866e]
stable/6.6: [0641908b906a133f1494c312a71f9fecbe2b6c78]
stable/6.8: [2f73cf2ae5e0f4e629db5be3a4380ff7807148e6]

CVE-2024-26976: KVM: Always flush async #PF workqueue when vCPU is
being destroyed

Announce: https://lore.kernel.org/linux-cve-announce/2024050133-CVE-2024-26976-60d4@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit af585b9 ("KVM: Halt vcpu if page it tries to
access is swapped out") in v2.6.38-rc1.
Fixed in v6.9-rc1.

Fixed status
cip/4.4: [b795785f4f94c38971e329d43d6cbaab7f2a0b82]
cip/4.4-st: [b795785f4f94c38971e329d43d6cbaab7f2a0b82]
mainline: [3d75b8aa5c29058a512db29da7cbee8052724157]
stable/4.19: [ab2c2f5d9576112ad22cfd3798071cb74693b1f5]
stable/5.10: [f8730d6335e5f43d09151fca1f0f41922209a264]
stable/5.15: [83d3c5e309611ef593e2fcb78444fc8ceedf9bac]
stable/5.4: [82e25cc1c2e93c3023da98be282322fc08b61ffb]
stable/6.1: [b54478d20375874aeee257744dedfd3e413432ff]
stable/6.6: [a75afe480d4349c524d9c659b1a5a544dbc39a98]
stable/6.8: [caa9af2e27c275e089d702cfbaaece3b42bca31b]

CVE-2024-26977: pci_iounmap(): Fix MMIO mapping leak

Announce: https://lore.kernel.org/linux-cve-announce/2024050133-CVE-2024-26977-cf63@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 316e8d7 ("pci_iounmap'2: Electric Boogaloo: try
to make sense of it all") in v5.15-rc2.
This commit is not backported to older kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [7626913652cc786c238e2dd7d8740b17d41b2637]
stable/5.15: [5e4b23e7a7b33a1e56bfa3e5598138a2234d55b6]
stable/6.1: [6d21d0356aa44157a62e39c0d1a13d4c69a8d0c8]
stable/6.6: [b5d40f02e7222da032c2042aebcf2a07de9b342f]
stable/6.8: [af280e137e273935f2e09f4d73169998298792ed]

CVE-2024-26978: serial: max310x: fix NULL pointer dereference in I2C
instantiation

Announce: https://lore.kernel.org/linux-cve-announce/2024050133-CVE-2024-26978-cc0d@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 2e1f2d9 ("serial: max310x: implement I2C
support") in v6.0-rc1.
This commit was backported to 5.10 and 5.4.
Fixed in v6.9-rc1.

Fixed status
mainline: [0d27056c24efd3d63a03f3edfbcfc4827086b110]
stable/5.10: [c45e53c27b78afd6c81fc25608003576f27b5735]
stable/5.4: [7d271b798add90c6196539167c019d0817285cf0]
stable/6.1: [12609c76b755dbeb1645c0aacc0f0f4743b2eff3]
stable/6.6: [2160ad6861c4a21d3fa553d7b2aaec6634a37f8a]
stable/6.8: [aeca49661fd02fd56fb026768b580ce301b45733]

CVE-2024-26979: drm/vmwgfx: Fix possible null pointer derefence with
invalid contexts

Announce: https://lore.kernel.org/linux-cve-announce/2024050134-CVE-2024-26979-43e8@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 9c079b8 ("drm/vmwgfx: Adapt execbuf to the new
validation api") in v4.20-rc1.
This commit was backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [517621b7060096e48e42f545fa6646fc00252eac]
stable/5.10: [c560327d900bab968c2e1b4cd7fa2d46cd429e3d]
stable/5.15: [899e154f9546fcae18065d74064889d08fff62c2]
stable/6.1: [07c3fe923ff7eccf684fb4f8c953d0a7cc8ded73]
stable/6.6: [ff41e0d4f3fa10d7cdd7d40f8026bea9fcc8b000]
stable/6.8: [585fec7361e7850bead21fada49a7fcde2f2e791]

CVE-2024-26980: ksmbd: fix slab-out-of-bounds in smb2_allocate_rsp_buf

Announce: https://lore.kernel.org/linux-cve-announce/2024050141-CVE-2024-26980-4b16@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.9-rc6.
It looks this bug was introduced by commit 0626e66 ("cifsd: add server
handler for central processing and tranport layers") in 5.15-rc1.

Fixed status
mainline: [c119f4ede3fa90a9463f50831761c28f989bfb20]
stable/6.1: [b80ba648714e6d790d69610cf14656be222d0248]
stable/6.6: [3160d9734453a40db248487f8204830879c207f1]
stable/6.8: [0977f89722eceba165700ea384f075143f012085]

CVE-2024-26981: nilfs2: fix OOB in nilfs_set_de_type

Announce: https://lore.kernel.org/linux-cve-announce/2024050141-CVE-2024-26981-db53@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 2ba466d ("nilfs2: directory entry operations") in
v2.6.30-rc1.

Fixed in v6.9-rc5.

Fixed status
mainline: [c4a7dc9523b59b3e73fd522c73e95e072f876b16]
stable/5.15: [bdbe483da21f852c93b22557b146bc4d989260f0]
stable/6.1: [897ac5306bbeb83e90c437326f7044c79a17c611]
stable/6.6: [2382eae66b196c31893984a538908c3eb7506ff9]
stable/6.8: [90823f8d9ecca3d5fa6b102c8e464c62f416975f]

CVE-2024-26982: Squashfs: check the inode number is not the invalid
value of zero

Announce: https://lore.kernel.org/linux-cve-announce/2024050141-CVE-2024-26982-8675@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.9-rc5.
It seems to be all stable kernels are affected.

Fixed status
mainline: [9253c54e01b6505d348afbc02abaa4d9f8a01395]
stable/6.8: [7def00ebc9f2d6a581ddf46ce4541f84a10680e5]

CVE-2024-26983: bootconfig: use memblock_free_late to free xbc memory to buddy

Announce: https://lore.kernel.org/linux-cve-announce/2024050142-CVE-2024-26983-9424@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 40caa12 ("init: bootconfig: Remove all bootconfig
data when the init memory is removed") in v5.15-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc5.

Fixed status
mainline: [89f9a1e876b5a7ad884918c03a46831af202c8a0]
stable/6.1: [1e7feb31a18c197d63a5e606025ed63c762f8918]
stable/6.6: [e46d3be714ad9652480c6db129ab8125e2d20ab7]
stable/6.8: [5a7dfb8fcd3f29fc93161100179b27f24f3d5f35]

CVE-2024-26984: nouveau: fix instmem race condition around ptr stores

Announce: https://lore.kernel.org/linux-cve-announce/2024050142-CVE-2024-26984-3028@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit be55287 ("drm/nouveau/imem/nv50: embed
nvkm_instobj directly into nv04_instobj") in v4.15-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc5.

Fixed status
mainline: [fff1386cc889d8fb4089d285f883f8cba62d82ce]
stable/5.15: [3ab056814cd8ab84744c9a19ef51360b2271c572]
stable/6.1: [ad74d208f213c06d860916ad40f609ade8c13039]
stable/6.6: [a019b44b1bc6ed224c46fb5f88a8a10dd116e525]
stable/6.8: [21ca9539f09360fd83654f78f2c361f2f5ddcb52]

CVE-2024-26985: drm/xe: Fix bo leak in intel_fb_bo_framebuffer_init

Announce: https://lore.kernel.org/linux-cve-announce/2024050142-CVE-2024-26985-37ac@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 44e6949 ("drm/xe/display: Implement display
support") in v6.8-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc5.

Fixed status
mainline: [652ead9b746a63e4e79d7ad66d3edf0a8a5b0c2f]
stable/6.8: [7d8ac0942c312abda43b407eff72d31747a7b472]

CVE-2024-26986: drm/amdkfd: Fix memory leak in create_process failure

Announce: https://lore.kernel.org/linux-cve-announce/2024050142-CVE-2024-26986-4650@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 0ab2d75 ("drm/amdkfd: prepare per-process debug
enable and disable") in v6.5-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc5.

Fixed status
mainline: [18921b205012568b45760753ad3146ddb9e2d4e2]
stable/6.6: [aa02d43367a9adf8c85fb382fea4171fb266c8d0]
stable/6.8: [0dcd876411644da98a6b4d5a18d32ca94c15bdb5]

CVE-2024-26987: mm/memory-failure: fix deadlock when
hugetlb_optimize_vmemmap is enabled

Announce: https://lore.kernel.org/linux-cve-announce/2024050143-CVE-2024-26987-507c@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit a6b4085 ("mm: hugetlb: replace
hugetlb_free_vmemmap_enabled with a static_key") in v5.18-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc5.

Fixed status
mainline: [1983184c22dd84a4d95a71e5c6775c2638557dc7]
stable/6.1: [5ef7ba2799a3b5ed292b8f6407376e2c25ef002e]
stable/6.6: [882e1180c83f5b75bae03d0ccc31ccedfe5159de]
stable/6.8: [49955b24002dc16a0ae2e83a57a2a6c863a1845c]

CVE-2024-26988: init/main.c: Fix potential static_command_line memory overflow

Announce: https://lore.kernel.org/linux-cve-announce/2024050143-CVE-2024-26988-c304@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit f5c7310 ("init/main: add checks for the return
value of memblock_alloc*()") in v5.1-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc5.

Fixed status
mainline: [46dad3c1e57897ab9228332f03e1c14798d2d3b9]
stable/5.15: [0dc727a4e05400205358a22c3d01ccad2c8e1fe4]
stable/6.1: [76c2f4d426a5358fced5d5990744d46f10a4ccea]
stable/6.6: [81cf85ae4f2dd5fa3e43021782aa72c4c85558e8]
stable/6.8: [936a02b5a9630c5beb0353c3085cc49d86c57034]

CVE-2024-26989: arm64: hibernate: Fix level3 translation fault in swsusp_save()

Announce: https://lore.kernel.org/linux-cve-announce/2024050143-CVE-2024-26989-851d@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit a7d9f30 ("arm64: drop pfn_valid_within() and
simplify pfn_valid()") in v5.14-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc5.

Fixed status
mainline: [50449ca66cc5a8cbc64749cf4b9f3d3fc5f4b457]
stable/5.15: [813f5213f2c612dc800054859aaa396ec8ad7069]
stable/6.1: [f7e71a7cf399f53ff9fc314ca3836dc913b05bd6]
stable/6.6: [31f815cb436082e72d34ed2e8a182140a73ebdf4]
stable/6.8: [022b19ebc31cce369c407617041a3db810db23b3]

CVE-2024-26990: KVM: x86/mmu: Write-protect L2 SPTEs in TDP MMU when
clearing dirty status

Announce: https://lore.kernel.org/linux-cve-announce/2024050143-CVE-2024-26990-0a1f@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 5982a53 ("KVM: x86/mmu: Use kvm_ad_enabled() to
determine if TDP MMU SPTEs need wrprot") in v6.4-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc5.

Fixed status
mainline: [2673dfb591a359c75080dd5af3da484b89320d22]
stable/6.6: [cdf811a937471af2d1facdf8ae80e5e68096f1ed]
stable/6.8: [e20bff0f1b2de9cfe303dd35ff46470104a87404]

CVE-2024-26991: KVM: x86/mmu: x86: Don't overflow lpage_info when
checking attributes

Announce: https://lore.kernel.org/linux-cve-announce/2024050144-CVE-2024-26991-f6d3@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 90b4fe1 ("KVM: x86: Disallow hugepages when
memory attributes are mixed") in v6.8-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc5.

Fixed status
mainline: [992b54bd083c5bee24ff7cc35991388ab08598c4]
stable/6.8: [048cc4a028e635d339687ed968985d2d1669494c]

CVE-2024-26992: KVM: x86/pmu: Disable support for adaptive PEBS

Announce: https://lore.kernel.org/linux-cve-announce/2024050144-CVE-2024-26992-4f0e@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit c59a1f1 ("KVM: x86/pmu: Add IA32_PEBS_ENABLE MSR
emulation for extended PEBS") in v6.0-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc5.

Fixed status
mainline: [9e985cbf2942a1bb8fcef9adc2a17d90fd7ca8ee]
stable/6.1: [0fb74c00d140a66128afc0003785dcc57e69d312]
stable/6.6: [037e48ceccf163899374b601afb6ae8d0bf1d2ac]
stable/6.8: [7a7650b3ac23e5fc8c990f00e94f787dc84e3175]

CVE-2024-26993: fs: sysfs: Fix reference leak in sysfs_break_active_protection()

Announce: https://lore.kernel.org/linux-cve-announce/2024050144-CVE-2024-26993-fe52@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 2afc916 ("scsi: sysfs: Introduce
sysfs_{un,}break_active_protection()") in v4.19-rc1.
This commit was backported to 4.4.
Fixed in v6.9-rc5.

Fixed status
mainline: [a90bca2228c0646fc29a72689d308e5fe03e6d78]
stable/5.15: [43f00210cb257bcb0387e8caeb4b46375d67f30c]
stable/6.1: [5d43e072285e81b0b63cee7189b3357c7768a43b]
stable/6.6: [ac107356aabc362aaeb77463e814fc067a5d3957]
stable/6.8: [a4c99b57d43bab45225ba92d574a8683f9edc8e4]

CVE-2024-26994: speakup: Avoid crash on very long word

Announce: https://lore.kernel.org/linux-cve-announce/2024050144-CVE-2024-26994-43c6@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit c6e3fd2 ("Staging: add speakup to the staging
directory") in v2.6.37-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc5.

Fixed status
mainline: [c8d2f34ea96ea3bce6ba2535f867f0d4ee3b22e1]
stable/5.15: [0d130158db29f5e0b3893154908cf618896450a8]
stable/6.1: [89af25bd4b4bf6a71295f07e07a8ae7dc03c6595]
stable/6.6: [8defb1d22ba0395b81feb963b96e252b097ba76f]
stable/6.8: [0efb15c14c493263cb3a5f65f5ddfd4603d19a76]

CVE-2024-26995: usb: typec: tcpm: Correct the PDO counting in pd_set

Announce: https://lore.kernel.org/linux-cve-announce/2024050144-CVE-2024-26995-ac9b@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit cd099cd ("usb: typec: tcpm: Support multiple
capabilities") in v6.8-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc5.

Fixed status
mainline: [c4128304c2169b4664ed6fb6200f228cead2ab70]
stable/6.8: [f3da3192cdd3fefe213390e976eec424a8e270b5]

CVE-2024-26996: usb: gadget: f_ncm: Fix UAF ncm object at re-bind
after usb ep transport error

Announce: https://lore.kernel.org/linux-cve-announce/2024050145-CVE-2024-26996-ff2f@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.9-rc5.
It looks as if all stable kernels are affected.

Fixed status
mainline: [6334b8e4553cc69f51e383c9de545082213d785e]
stable/5.15: [7f67c2020cb08499c400abf0fc32c65e4d9a09ca]
stable/6.1: [0588bbbd718a8130b98c54518f1e0b569ce60a93]
stable/6.6: [f356fd0cbd9c9cbd0854657a80d1608d0d732db3]
stable/6.8: [7250326cbb1f4f90391ac511a126b936cefb5bb7]

CVE-2024-26997: usb: dwc2: host: Fix dereference issue in DDMA completion flow.

Announce: https://lore.kernel.org/linux-cve-announce/2024050145-CVE-2024-26997-b8bf@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit b258e42 ("usb: dwc2: host: Fix ISOC flow in DDMA
mode") in v6.9-rc2.
This commit was backported to stable kernels except 4.4.
Fixed in v6.9-rc5.

Fixed status
mainline: [eed04fa96c48790c1cce73c8a248e9d460b088f8]
stable/5.15: [8aa5c28ac65cb5e7f1b9c0c3238c00b661dd2b8c]
stable/6.1: [9de10b59d16880a0a3ae2876c142fe54ce45d816]
stable/6.6: [8a139fa44870e84ac228b7b76423a49610e5ba9a]
stable/6.8: [55656b2afd5f1efcec4245f3e7e814c2a9ef53f6]

CVE-2024-26998: serial: core: Clearing the circular buffer before NULLifying it

Announce: https://lore.kernel.org/linux-cve-announce/2024050145-CVE-2024-26998-2262@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 43066e3 ("serial: port: Don't suspend if the port
is still busy") in v6.8.
This commit was backported to 6.6.
Fixed in v6.9-rc5.

Fixed status
mainline: [9cf7ea2eeb745213dc2a04103e426b960e807940]
stable/6.6: [7ae7104d54342433a3a73975f6569beefdd86350]
stable/6.8: [bb1118905e875c111d7ccef9aee86ac5e4e7f985]

CVE-2024-26999: serial/pmac_zilog: Remove flawed mitigation for rx irq flood

Announce: https://lore.kernel.org/linux-cve-announce/2024050145-CVE-2024-26999-057f@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 1da177e ("Linux-2.6.12-rc2") in v2.6.12.
Fixed in v6.9-rc5.

Fixed status
mainline: [1be3226445362bfbf461c92a5bcdb1723f2e4907]
stable/5.15: [7a3bbe41efa55323b6ea3c35fa15941d4dbecdef]
stable/6.1: [bbaafbb4651fede8d3c3881601ecaa4f834f9d3f]
stable/6.6: [52aaf1ff14622a04148dbb9ccce6d9de5d534ea7]
stable/6.8: [ca09dfc3cfdf89e6af3ac24e1c6c0be5c575a729]

CVE-2024-27000: serial: mxs-auart: add spinlock around changing cts state

Announce: https://lore.kernel.org/linux-cve-announce/2024050146-CVE-2024-27000-c789@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 4d90bb1 ("serial: core: Document and assert lock
requirements for irq helpers") in v3.18-rc1.
Fixed in v6.9-rc5.

Fixed status
mainline: [54c4ec5f8c471b7c1137a1f769648549c423c026]
stable/6.1: [2c9b943e9924cf1269e44289bc5e60e51b0f5270]
stable/6.6: [5f40fd6ca2cf0bfbc5a5c9e403dfce8ca899ba37]
stable/6.8: [94b0e65c75f4af888ab2dd6c90f060f762924e86]

CVE-2024-27001: comedi: vmk80xx: fix incomplete endpoint checking

Announce: https://lore.kernel.org/linux-cve-announce/2024050146-CVE-2024-27001-16ca@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 49253d5 ("staging: comedi: vmk80xx: factor out
usb endpoint detection") in v3.9-rc1.
Fixed in v6.9-rc5.

Fixed status
mainline: [d1718530e3f640b7d5f0050e725216eab57a85d8]
stable/5.15: [b0b268eeb087e324ef3ea71f8e6cabd07630517f]
stable/6.1: [ac882d6b21bffecb57bcc4486701239eef5aa67b]
stable/6.6: [59f33af9796160f851641d960bd93937f282c696]
stable/6.8: [6ec3514a7d35ad9cfab600187612c29f669069d2]

CVE-2024-27002: clk: mediatek: Do a runtime PM get on controllers during probe

Announce: https://lore.kernel.org/linux-cve-announce/2024050146-CVE-2024-27002-3b11@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit acddfc2 ("clk: mediatek: Add MT8183 clock
support") in v5.2-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc5.

Fixed status
mainline: [2f7b1d8b5505efb0057cd1ab85fca206063ea4c3]
stable/6.1: [165d226472575b213dd90dfda19d1605dd7c19a8]
stable/6.6: [c0dcd5c072e2a3fff886f673e6a5d9bf8090c4cc]
stable/6.8: [b62ed25feb342eab052822eff0c554873799a4f5]

CVE-2024-27003: clk: Get runtime PM before walking tree for clk_summary

Announce: https://lore.kernel.org/linux-cve-announce/2024050146-CVE-2024-27003-c862@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 1bb294a ("clk: Enable/Disable runtime PM for
clk_summary") in v5.17-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc5.

Fixed status
mainline: [9d1e795f754db1ac3344528b7af0b17b8146f321]
stable/6.1: [83ada89e4a86e2b28ea2b5113c76d6dc7560a4d0]
stable/6.6: [2c077fdfd09dffb31a890e5095c8ab205138a42e]
stable/6.8: [b457105309d388e4081c716cf7b81d517ff74db4]

CVE-2024-27004: clk: Get runtime PM before walking tree during disable_unused

Announce: https://lore.kernel.org/linux-cve-announce/2024050147-CVE-2024-27004-c429@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 9a34b45 ("clk: Add support for runtime PM") in v4.15-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc5.

Fixed status
mainline: [e581cf5d216289ef292d1a4036d53ce90e122469]
stable/5.15: [a29ec0465dce0b871003698698ac6fa92c9a5034]
stable/6.1: [a424e713e0cc33d4b969cfda25b9f46df4d7b5bc]
stable/6.6: [60ff482c4205a5aac3b0595ab794cfd62295dab5]
stable/6.8: [115554862294397590088ba02f11f2aba6d5016c]

CVE-2024-27005: interconnect: Don't access req_list while it's being manipulated

Announce: https://lore.kernel.org/linux-cve-announce/2024050147-CVE-2024-27005-e630@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit af42269 ("interconnect: Fix locking for runpm vs
reclaim") in v6.6-rc1.
This commit is backported to 5.15 and 6.1.
Fixed in v6.9-rc5.

Fixed status
mainline: [de1bf25b6d771abdb52d43546cf57ad775fb68a1]
stable/6.6: [d0d04efa2e367921654b5106cc5c05e3757c2b42]
stable/6.8: [4c65507121ea8e0b47fae6d2049c8688390d46b6]

CVE-2024-27006: thermal/debugfs: Add missing count increment to
thermal_debug_tz_trip_up()

Announce: https://lore.kernel.org/linux-cve-announce/2024050147-CVE-2024-27006-3b6f@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 7ef01f2 ("thermal/debugfs: Add thermal debugfs
information for mitigation episodes") in v6.8-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc5.

Fixed status
mainline: [b552f63cd43735048bbe9bfbb7a9dcfce166fbdd]
stable/6.8: [9c8215d32e730b597c809a9d2090bf8ec1b79fcf]

CVE-2024-27007: userfaultfd: change src_folio after ensuring it's
unpinned in UFFDIO_MOVE

Announce: https://lore.kernel.org/linux-cve-announce/2024050147-CVE-2024-27007-686b@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit adef440 ("userfaultfd: UFFDIO_MOVE uABI") in v6.8-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc5.

Fixed status
mainline: [c0205eaf3af9f5db14d4b5ee4abacf4a583c3c50]
stable/6.8: [df5f6e683e7f21a15d8be6e7a0c7a46436963ebe]

CVE-2024-27008: drm: nv04: Fix out of bounds access

Announce: https://lore.kernel.org/linux-cve-announce/2024050148-CVE-2024-27008-5964@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 2e5702a ("drm/nouveau: fabricate DCB encoder
table for iMac G4") in v2.6.38-rc1.
Introduced by commit 670820c ("drm/nouveau: Workaround incorrect DCB
entry on a GeForce3 Ti 200.") in v2.6.38-rc3.
Fixed in v6.9-rc5.

Fixed status
mainline: [cf92bb778eda7830e79452c6917efa8474a30c1e]
stable/5.15: [df0991da7db846f7fa4ec6740350f743d3b69b04]
stable/6.1: [5fd4b090304e450aa0e7cc9cc2b4873285c6face]
stable/6.6: [6690cc2732e2a8d0eaca44dcbac032a4b0148042]
stable/6.8: [26212da39ee14a52c76a202c6ae5153a84f579a5]

CVE-2024-27009: s390/cio: fix race condition during online processing

Announce: https://lore.kernel.org/linux-cve-announce/2024050148-CVE-2024-27009-d63d@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 2297791 ("s390/cio: dont unregister subchannel
from child-drivers") in v5.15-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc5.

Fixed status
mainline: [2d8527f2f911fab84aec04df4788c0c23af3df48]
stable/5.15: [3076b3c38a704e10df5e143c213653309d532538]
stable/6.1: [559f3a6333397ab6cd4a696edd65a70b6be62c6e]
stable/6.6: [2df56f4ea769ff81e51bbb05699989603bde9c49]
stable/6.8: [a4234decd0fe429832ca81c4637be7248b88b49e]

CVE-2024-27010: net/sched: Fix mirred deadlock on device recursion

Announce: https://lore.kernel.org/linux-cve-announce/2024050148-CVE-2024-27010-5a68@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 3bcb846 ("net: get rid of spin_trylock() in
net_tx_action()") in v4.8-rc1.
Introduced by commit e578d9c ("net: sched: use counter to break
reclassify loops") in v4.2-rc1.
Fixed in v6.9-rc5.

Fixed status
mainline: [0f022d32c3eca477fbf79a205243a6123ed0fe11]
stable/6.8: [e6b90468da4dae2281a6e381107f411efb48b0ef]

CVE-2024-27011: netfilter: nf_tables: fix memleak in map from abort path

Announce: https://lore.kernel.org/linux-cve-announce/2024050148-CVE-2024-27011-2c70@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 5910544 ("netfilter: nf_tables: revisit
chain/object refcounting from elements") in v4.12-rc3.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc5.

Fixed status
mainline: [86a1471d7cde792941109b93b558b5dc078b9ee9]
stable/6.8: [49d0e656d19dfb2d4d7c230e4a720d37b3decff6]

CVE-2024-27012: netfilter: nf_tables: restore set elements when delete set fails

Announce: https://lore.kernel.org/linux-cve-announce/2024050148-CVE-2024-27012-5564@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 628bd3e ("netfilter: nf_tables: drop map element
references from preparation phase") in v6.4.
This commit was backported to 5.10, 5.15, 5.4, and 6.1.
Fixed in v6.9-rc5.

Fixed status
mainline: [e79b47a8615d42c68aaeb68971593333667382ed]
stable/6.8: [86658fc7414d4b9e25c2699d751034537503d637]

CVE-2024-27013: tun: limit printing rate when illegal packet received by tun dev

Announce: https://lore.kernel.org/linux-cve-announce/2024050149-CVE-2024-27013-2c26@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit ef3db4a ("tun: avoid BUG, dump packet on GSO
errors") in v2.6.35.
Fixed in v6.9-rc5.

Fixed status
mainline: [f8bbc07ac535593139c875ffa19af924b1084540]
stable/5.15: [a50dbeca28acf7051dfa92786b85f704c75db6eb]
stable/6.1: [62e27ef18eb4f0d33bbae8e9ef56b99696a74713]
stable/6.6: [40f4ced305c6c47487d3cd8da54676e2acc1a6ad]
stable/6.8: [52854101180beccdb9dc2077a3bea31b6ad48dfa]

CVE-2024-27014: net/mlx5e: Prevent deadlock while disabling aRFS

Announce: https://lore.kernel.org/linux-cve-announce/2024050149-CVE-2024-27014-d2dc@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 45bf454 ("net/mlx5e: Enabling aRFS mechanism") in v4.7-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc5.

Fixed status
mainline: [fef965764cf562f28afb997b626fc7c3cec99693]
stable/6.1: [46efa4d5930cf3c2af8c01f75e0a47e4fc045e3b]
stable/6.6: [48c4bb81df19402d4346032353d0795260255e3b]
stable/6.8: [0080bf99499468030248ebd25dd645e487dcecdc]

CVE-2024-27015: netfilter: flowtable: incorrect pppoe tuple

Announce: https://lore.kernel.org/linux-cve-announce/2024050149-CVE-2024-27015-9ce1@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 72efd58 ("netfilter: flowtable: add pppoe
support") in v5.13-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc5.

Fixed status
mainline: [6db5dc7b351b9569940cd1cf445e237c42cd6d27]
stable/5.15: [e719b52d0c56989b0f3475a03a6d64f182c85b56]
stable/6.1: [f1c3c61701a0b12f4906152c1626a5de580ea3d2]
stable/6.6: [4ed82dd368ad883dc4284292937b882f044e625d]
stable/6.8: [e3f078103421642fcd5f05c5e70777feb10f000d]

CVE-2024-27016: netfilter: flowtable: validate pppoe header

Announce: https://lore.kernel.org/linux-cve-announce/2024050149-CVE-2024-27016-5114@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 72efd58 ("netfilter: flowtable: add pppoe
support") in v5.13-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc5.

Fixed status
mainline: [87b3593bed1868b2d9fe096c01bcdf0ea86cbebf]
stable/5.15: [d06977b9a4109f8738bb276125eb6a0b772bc433]
stable/6.1: [8bf7c76a2a207ca2b4cfda0a279192adf27678d7]
stable/6.6: [a2471d271042ea18e8a6babc132a8716bb2f08b9]
stable/6.8: [cf366ee3bc1b7d1c76a882640ba3b3f8f1039163]

CVE-2024-27017: netfilter: nft_set_pipapo: walk over current view on
netlink dump

Announce: https://lore.kernel.org/linux-cve-announce/2024050150-CVE-2024-27017-d867@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 2b84e21 ("netfilter: nft_set_pipapo: .walk does
not deal with generations") in v6.4.
This commit was backported to 5.10, 5.15, and 6.1.
Fixed in v6.9-rc5.

Fixed status
mainline: [29b359cf6d95fd60730533f7f10464e95bd17c73]
stable/6.8: [721715655c72640567e8742567520c99801148ed]

CVE-2024-27018: netfilter: br_netfilter: skip conntrack input hook for
promisc packets

Announce: https://lore.kernel.org/linux-cve-announce/2024050150-CVE-2024-27018-d8a7@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 62e7151 ("netfilter: bridge: confirm multicast
packets before passing them up the stack") in v6.8-rc7.
This commit was backported to 5.15, 6.1, and 6.6.
Fixed in v6.9-rc5.

Fixed status
mainline: [751de2012eafa4d46d8081056761fa0e9cc8a178]
stable/5.15: [dceb683ab87ca3666a9bb5c0158528b646faedc4]
stable/6.1: [b13db0d16bc7b2a52abcf5cb71334f63faa5dbd6]
stable/6.6: [3f59ac29dea0921637053908fe99268d157bbb9d]
stable/6.8: [43193174510ea4f3ce09b796e559a2fd9f148615]

CVE-2024-27019: netfilter: nf_tables: Fix potential data-race in
__nft_obj_type_get()

Announce: https://lore.kernel.org/linux-cve-announce/2024050150-CVE-2024-27019-e3d4@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit e500924 ("netfilter: nf_tables: add stateful
objects") in v4.10-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc5.

Fixed status
mainline: [d78d867dcea69c328db30df665be5be7d0148484]
stable/5.15: [379bf7257bc5f2a1b1ca8514e08a871b7bf6d920]
stable/6.1: [df7c0fb8c2b9f9cac65659332581b19682a71349]
stable/6.6: [ad333578f736d56920e090d7db1f8dec891d815e]
stable/6.8: [4ca946b19caf655a08d5e2266d4d5526025ebb73]

CVE-2024-27020: netfilter: nf_tables: Fix potential data-race in
__nft_expr_type_get()

Announce: https://lore.kernel.org/linux-cve-announce/2024050150-CVE-2024-27020-5158@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit ef1f7df ("netfilter: nf_tables: expression ops
overloading") in v3.13-rc1.
Fixed in v6.9-rc5.

Fixed status
mainline: [f969eb84ce482331a991079ab7a5c4dc3b7f89bf]
stable/5.15: [0b6de00206adbbfc6373b3ae38d2a6f197987907]
stable/6.1: [8d56bad42ac4c43c6c72ddd6a654a2628bf839c5]
stable/6.6: [a9ebf340d123ae12582210407f879d6a5a1bc25b]
stable/6.8: [01f1a678b05ade4b1248019c2dcca773aebbeb7f]

CVE-2024-27021: r8169: fix LED-related deadlock on module removal

Announce: https://lore.kernel.org/linux-cve-announce/2024050151-CVE-2024-27021-6a83@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 18764b8 ("r8169: add support for LED's on
RTL8168/RTL8101") in v6.8-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc4.

Fixed status
mainline: [19fa4f2a85d777a8052e869c1b892a2f7556569d]
stable/6.8: [53d986f39acd8ea11c9e460732bfa5add66360d9]

CVE-2024-27022: fork: defer linking file vma until vma is fully initialized

Announce: https://lore.kernel.org/linux-cve-announce/2024050143-CVE-2024-27022-4325@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 8d9bfb2 ("hugetlb: add vma based lock for pmd
sharing") in v6.1-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc5.

Fixed status
mainline: [35e351780fa9d8240dd6f7e4f245f9ea37e96c19]
stable/6.8: [abdb88dd272bbeb93efe01d8e0b7b17e24af3a34]

CVE-2024-27023: md: Fix missing release of 'active_io' for flush

Announce: https://lore.kernel.org/linux-cve-announce/2024050105-CVE-2024-27023-4810@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit fa2bbff ("md: synchronize flush io with array
reconfiguration") in 6.8-rc1.
This commit was backported to 6.1 and 6.6.
Fixed in 6.8-rc6.

Fixed status
mainline: [855678ed8534518e2b428bcbcec695de9ba248e8]
stable/6.1: [6b2ff10390b19a2364af622b6666b690443f9f3f]
stable/6.6: [02dad157ba11064d073f5499dc33552b227d5d3a]

CVE-2024-27024: net/rds: fix WARNING in rds_conn_connect_if_down

Announce: https://lore.kernel.org/linux-cve-announce/2024050107-CVE-2024-27024-efbd@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 584a827 ("RDS: RDMA: return appropriate error on
rdma map failures") in v4.11-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8.

Fixed status
mainline: [c055fc00c07be1f0df7375ab0036cebd1106ed38]
stable/4.19: [786854141057751bc08eb26f1b02e97c1631c8f4]
stable/5.10: [9dfc15a10dfd44f8ff7f27488651cb5be6af83c2]
stable/5.15: [b562ebe21ed9adcf42242797dd6cb75beef12bf0]
stable/5.4: [997efea2bf3a4adb96c306b9ad6a91442237bf5b]
stable/6.1: [998fd719e6d6468b930ac0c44552ea9ff8b07b80]
stable/6.6: [2b505d05280739ce31d5708da840f42df827cb85]
stable/6.8: [c055fc00c07be1f0df7375ab0036cebd1106ed38]

CVE-2024-27025: nbd: null check for nla_nest_start

Announce: https://lore.kernel.org/linux-cve-announce/2024050107-CVE-2024-27025-babd@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 47d902b ("nbd: add a status netlink command") in v4.12-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [31edf4bbe0ba27fd03ac7d87eb2ee3d2a231af6d]
stable/5.10: [4af837db0fd3679fabc7b7758397090b0c06dced]
stable/5.15: [98e60b538e66c90b9a856828c71d4e975ebfa797]
stable/5.4: [44214d744be32a4769faebba764510888f1eb19e]
stable/6.1: [96436365e5d80d0106ea785a4f80a58e7c9edff8]
stable/6.6: [b7f5aed55829f376e4f7e5ea5b80ccdcb023e983]
stable/6.8: [ba6a9970ce9e284cbc04099361c58731e308596a]

CVE-2024-27026: vmxnet3: Fix missing reserved tailroom

Announce: https://lore.kernel.org/linux-cve-announce/2024050108-CVE-2024-27026-189b@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 54f00cc ("vmxnet3: Add XDP support.") in v6.6-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [e127ce7699c1e05279ee5ee61f00893e7bfa9671]
stable/6.6: [aba8659caf88017507419feea06069f529329ea6]
stable/6.8: [91d017d19d5a9ad153e2dc23ed3c0e2e79ef5262]

CVE-2024-27027: dpll: fix dpll_xa_ref_*_del() for multiple registrations

Announce: https://lore.kernel.org/linux-cve-announce/2024050108-CVE-2024-27027-ba6a@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 9431063 ("dpll: core: Add DPLL framework base
functions") in v6.7-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [b446631f355ece73b13c311dd712c47381a23172]
stable/6.8: [b27e32e9367dac024cd6f61f22655714f483fd67]

CVE-2024-27028: spi: spi-mt65xx: Fix NULL pointer access in interrupt handler

Announce: https://lore.kernel.org/linux-cve-announce/2024050110-CVE-2024-27028-42f0@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 1ce2486 ("spi: mediatek: Only do dma for 4-byte
aligned buffers") in v4.11-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [a20ad45008a7c82f1184dc6dee280096009ece55]
stable/4.19: [2342b05ec5342a519e00524a507f7a6ea6791a38]
stable/5.10: [bcfcdf19698024565eff427706ebbd8df65abd11]
stable/5.15: [c10fed329c1c104f375a75ed97ea3abef0786d62]
stable/5.4: [55f8ea6731aa64871ee6aef7dba53ee9f9f3b2f6]
stable/6.1: [766ec94cc57492eab97cbbf1595bd516ab0cb0e4]
stable/6.6: [62b1f837b15cf3ec2835724bdf8577e47d14c753]
stable/6.8: [1784053cf10a14c4ebd8a890bad5cfe1bee51713]

CVE-2024-27029: drm/amdgpu: fix mmhub client id out-of-bounds access

Announce: https://lore.kernel.org/linux-cve-announce/2024050110-CVE-2024-27029-69f0@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit aba2be4 ("drm/amdgpu: add mmhub 3.3.0 support")
in v6.7-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [6540ff6482c1a5a6890ae44b23d0852ba1986d9e]
stable/6.8: [1f24b3040f2b6ffcb97151fabb3070328254d923]

CVE-2024-27030: octeontx2-af: Use separate handlers for interrupts

Announce: https://lore.kernel.org/linux-cve-announce/2024050110-CVE-2024-27030-d75a@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 7304ac4 ("octeontx2-af: Add mailbox IRQ and msg
handlers") in v4.20-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [50e60de381c342008c0956fd762e1c26408f372c]
stable/5.10: [766c2627acb2d9d1722cce2e24837044d52d888a]
stable/5.15: [772f18ded0e240cc1fa2b7020cc640e3e5c32b70]
stable/5.4: [94cb17e5cf3a3c484063abc0ce4b8a2b2e8c1cb2]
stable/6.1: [29d2550d79a8cbd31e0fbaa5c0e2a2efdc444e44]
stable/6.6: [dc29dd00705a62c77de75b6d752259b869aac49d]
stable/6.8: [4fedae8f9eafa2ac8cdaca58e315f52a7e2a8701]

CVE-2024-27031: NFS: Fix nfs_netfs_issue_read() xarray locking for
writeback interrupt

Announce: https://lore.kernel.org/linux-cve-announce/2024050110-CVE-2024-27031-2e85@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 000dbe0 ("NFS: Convert buffered read paths to use
netfs when fscache is enabled") in v6.4-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [fd5860ab6341506004219b080aea40213b299d2e]
stable/6.6: [ad27382f8495f8ef6d2c66c413d756bfd13c0598]
stable/6.8: [8a2e5977cecd3cde6a0e3e86b7b914d00240e5dc]

CVE-2024-27032: f2fs: fix to avoid potential panic during recovery

Announce: https://lore.kernel.org/linux-cve-announce/2024050111-CVE-2024-27032-97a9@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 956fa1d ("f2fs: fix to check return value of
f2fs_reserve_new_block()") in v6.8-rc1.
This commit was backported to older stable kernels except 4.4.
Fixed in v6.9-rc1.

Fixed status
mainline: [21ec68234826b1b54ab980a8df6e33c74cfbee58]
stable/6.1: [fe4de493572a4263554903bf9c3afc5c196e15f0]
stable/6.6: [8844b2f8a3f0c428b74672f9726f9950b1a7764c]
stable/6.8: [f26091a981318b5b7451d61f99bc073a6af8db67]

CVE-2024-27033: f2fs: fix to remove unnecessary f2fs_bug_on() to avoid panic

Announce: https://lore.kernel.org/linux-cve-announce/2024050111-CVE-2024-27033-d152@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 18792e6 ("f2fs: support fault injection for
f2fs_is_valid_blkaddr()") in v6.2-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [b896e302f79678451a94769ddd9e52e954c64fbb]
stable/6.6: [0386408036bfc8b50296d9e544ff91c4d52af2db]
stable/6.8: [abe98a05e7162f64759bf9111108ebcb11322dec]

CVE-2024-27034: f2fs: compress: fix to cover normal cluster write with cp_rwsem

Announce: https://lore.kernel.org/linux-cve-announce/2024050111-CVE-2024-27034-5872@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 4c8ff70 ("f2fs: support data compression") in v5.6-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [fd244524c2cf07b5f4c3fe8abd6a99225c76544b]
stable/5.15: [7d420eaaa18ec8e2bb4eeab8c65c00492ef6f416]
stable/6.1: [542c8b3c774a480bfd0804291a12f6f2391b0cd1]
stable/6.6: [75abfd61392b1db391bde6d738a30d685b843286]
stable/6.8: [52982edfcefd475cc34af663d5c47c0cddaa5739]

CVE-2024-27035: f2fs: compress: fix to guarantee persisting compressed
blocks by CP

Announce: https://lore.kernel.org/linux-cve-announce/2024050111-CVE-2024-27035-1628@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 4c8ff70 ("f2fs: support data compression") in v5.6-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [8a430dd49e9cb021372b0ad91e60aeef9c6ced00]
stable/6.1: [e54cce8137258a550b49cae45d09e024821fb28d]
stable/6.6: [82704e598d7b33c7e45526e34d3c585426319bed]
stable/6.8: [57e8b17d0522c8f4daf0c4d9969b4d7358033532]

CVE-2024-27036: cifs: Fix writeback data corruption

Announce: https://lore.kernel.org/linux-cve-announce/2024050111-CVE-2024-27036-6ba3@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit d08089f ("cifs: Change the I/O paths to use an
iterator rather than a page list") in v6.3-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [f3dc1bdb6b0b0693562c7c54a6c28bafa608ba3c]
stable/6.6: [e45deec35bf7f1f4f992a707b2d04a8c162f2240]
stable/6.8: [844b4e132f57f1333dc79feaa035075a096762e4]

CVE-2024-27037: clk: zynq: Prevent null pointer dereference caused by
kmalloc failure

Announce: https://lore.kernel.org/linux-cve-announce/2024050112-CVE-2024-27037-d54a@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 0ee52b1 ("clk: zynq: Add clock controller
driver") in v3.11-rc1.
Fixed in v6.9-rc1.

Fixed status
mainline: [7938e9ce39d6779d2f85d822cc930f73420e54a6]
stable/5.15: [01511ac7be8e45f80e637f6bf61af2d3d2dee9db]
stable/6.1: [8c4889a9ea861d7be37463c10846eb75e1b49c9d]
stable/6.6: [0801c893fd48cdba66a3c8f44c3fe43cc67d3b85]
stable/6.8: [58a946ab43501f2eba058d24d96af0ad1122475b]

CVE-2024-27038: clk: Fix clk_core_get NULL dereference

Announce: https://lore.kernel.org/linux-cve-announce/2024050112-CVE-2024-27038-3af3@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit dde4eff ("clk: Look for parents with clkdev based
clk_lookups") in v5.2-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [e97fe4901e0f59a0bfd524578fe3768f8ca42428]
stable/5.10: [239174535dba11f7b83de0eaaa27909024f8c185]
stable/5.15: [0efb9ef6fb95384ba631d6819e66f10392aabfa2]
stable/5.4: [d7ae7d1265686b55832a445b1db8cdd69738ac07]
stable/6.1: [a8b2b26fdd011ebe36d68a9a321ca45801685959]
stable/6.6: [a5d9b1aa61b401867b9066d54086b3e4ee91f8ed]
stable/6.8: [6f073b24a9e2becd25ac4505a9780a87e621bb51]

CVE-2024-27039: clk: hisilicon: hi3559a: Fix an erroneous devm_kfree()

Announce: https://lore.kernel.org/linux-cve-announce/2024050112-CVE-2024-27039-3730@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 6c81966 ("clk: hisilicon: Add clock driver for
hi3559A SoC") in v5.14-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [64c6a38136b74a2f18c42199830975edd9fbc379]
stable/5.15: [3f8445f1c746fda180a7f75372ed06b24e9cefe2]
stable/6.1: [e0b0d1c46a2ce1e46b79d004a7270fdef872e097]
stable/6.6: [95d1f1228c1bb54803ae57525b76db60e99b37e4]
stable/6.8: [d575765b1b62e8bdb00af11caa1aabeb01763d9f]

CVE-2024-27040: drm/amd/display: Add 'replay' NULL check in
'edp_set_replay_allow_active()'

Announce: https://lore.kernel.org/linux-cve-announce/2024050112-CVE-2024-27040-e45b@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit c7ddc0a ("drm/amd/display: Add Functions to
enable Freesync Panel Replay") in v6.6-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [f6aed043ee5d75b3d1bfc452b1a9584b63c8f76b]
stable/6.6: [f610c46771ef1047e46d61807aa7c69cd29e63d8]
stable/6.8: [d0e94f4807ff0df66cf447d6b4bbb8ac830e99c3]

CVE-2024-27041: drm/amd/display: fix NULL checks for adev->dm.dc in
amdgpu_dm_fini()

Announce: https://lore.kernel.org/linux-cve-announce/2024050112-CVE-2024-27041-7bf4@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 81927e2 ("drm/amd/display: Support for DMUB AUX")
in v5.14-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [2a3cfb9a24a28da9cc13d2c525a76548865e182c]
stable/6.6: [e040f1fbe9abae91b12b074cfc3bbb5367b79811]
stable/6.8: [1c62697e4086de988b31124fb8c79c244ea05f2b]

CVE-2024-27042: drm/amdgpu: Fix potential out-of-bounds access in
'amdgpu_discovery_reg_base_init()'

Announce: https://lore.kernel.org/linux-cve-announce/2024050113-CVE-2024-27042-e812@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit a0ccc71 ("drm/amdgpu/discovery: validate VCN and
SDMA instances") in v5.19-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [cdb637d339572398821204a1142d8d615668f1e9]
stable/6.6: [8f3e68c6a3fff53c2240762a47a0045d89371775]
stable/6.8: [8db10cee51e3e11a6658742465edc21986cf1e8d]

CVE-2024-27043: media: edia: dvbdev: fix a use-after-free

Announce: https://lore.kernel.org/linux-cve-announce/2024050113-CVE-2024-27043-f2fb@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit b619010 ("V4L/DVB (5244): Dvbdev: fix illegal
re-usage of fileoperations struct") in v2.6.21-rc2.
Fixed in v6.9-rc1.

Fixed status
cip/4.4: [d87c1e726012e3ef1f738814267fd6f4bd5bc22b]
cip/4.4-st: [d87c1e726012e3ef1f738814267fd6f4bd5bc22b]
mainline: [8c64f4cdf4e6cc5682c52523713af8c39c94e6d5]
stable/4.19: [d0f5c28333822f9baa5280d813124920720fd856]
stable/5.10: [096237039d00c839f3e3a5fe6d001bf0db45b644]
stable/5.15: [0d3fe80b6d175c220b3e252efc6c6777e700e98e]
stable/5.4: [f20c3270f3ed5aa6919a87e4de9bf6c05fb57086]
stable/6.1: [437a111f79a2f5b2a5f21e27fdec6f40c8768712]
stable/6.6: [779e8db7efb22316c8581d6c229636d2f5694a62]
stable/6.8: [b7586e902128e4fb7bfbb661cb52e4215a65637b]

CVE-2024-27044: drm/amd/display: Fix potential NULL pointer
dereferences in 'dcn10_set_output_transfer_func()'

Announce: https://lore.kernel.org/linux-cve-announce/2024050113-CVE-2024-27044-7e0e@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit ddef02d ("drm/amd/display: add null checks before
logging") in v5.4-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [9ccfe80d022df7c595f1925afb31de2232900656]
stable/5.10: [330caa061af53ea6d287d7c43d0703714e510e08]
stable/5.15: [6ac7c7a3a9ab57aba0fe78ecb922d2b20e16efeb]
stable/5.4: [e019d87e02f1e539ae48b99187f253847744ca7a]
stable/6.1: [29fde8895b2fcc33f44aea28c644ce2d9b62f9e0]
stable/6.6: [2d9fe7787af01188dc470a649bdbb842d6511fd7]
stable/6.8: [7874ab3105ca4657102fee1cc14b0af70883c484]

CVE-2024-27045: drm/amd/display: Fix a potential buffer overflow in
'dp_dsc_clock_en_read()'

Announce: https://lore.kernel.org/linux-cve-announce/2024050113-CVE-2024-27045-6680@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit c06e09b ("drm/amd/display: Add DSC parameters
logging to debugfs") in v5.9-rc1.
This commit was not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [4b09715f1504f1b6e8dff0e9643630610bc05141]
stable/5.10: [ff28893c96c5e0927a4da10cd24a3522ca663515]
stable/5.15: [440f059837418fac1695b65d3ebc6080d33be877]
stable/6.1: [d346b3e5b25c95d504478507eb867cd3818775ab]
stable/6.6: [ad76fd30557d6a106c481e4606a981221ca525f7]
stable/6.8: [cf114d8d4a8d78df272116a745bb43b48cef65f4]

CVE-2024-27046: nfp: flower: handle acti_netdevs allocation failure

Announce: https://lore.kernel.org/linux-cve-announce/2024050113-CVE-2024-27046-4694@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit bb9a8d0 ("nfp: flower: monitor and offload LAG
groups") in v4.18-rc1.
This commit was not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [84e95149bd341705f0eca6a7fcb955c548805002]
stable/4.19: [d746889db75a76aeee95fb705b8e1ac28c684a2e]
stable/5.10: [928705e341010dd910fdece61ccb974f494a758f]
stable/5.15: [0d387dc503f9a53e6d1f6e9dd0292d38f083eba5]
stable/5.4: [3b1e8a617eb0f4cdc19def530047a95b5abde07d]
stable/6.1: [c9b4e220dd18f79507803f38a55d53b483f6c9c3]
stable/6.6: [408ba7fd04f959c61b50db79c983484312fea642]
stable/6.8: [9d8eb1238377cd994829f9162ae396a84ae037b2]

CVE-2024-27047: net: phy: fix phy_get_internal_delay accessing an empty array

Announce: https://lore.kernel.org/linux-cve-announce/2024050114-CVE-2024-27047-8aad@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 92252ee ("net: phy: Add a helper to return the
index for of the internal delay") in v5.9-rc1.
This commit was not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [4469c0c5b14a0919f5965c7ceac96b523eb57b79]
stable/5.10: [06dd21045a7e8bc8701b0ebedcd9a30a6325878b]
stable/5.15: [0e939a002c8a7d66e60bd0ea6b281fb39d713c1a]
stable/6.1: [2a2ff709511617de9c6c072eeee82bcbbdfecaf8]
stable/6.6: [589ec16174dd9378953b8232ae76fad0a96e1563]
stable/6.8: [0307cf443308ecc6be9b2ca312bb31bae5e5a7ad]

CVE-2024-27048: wifi: brcm80211: handle pmk_op allocation failure

Announce: https://lore.kernel.org/linux-cve-announce/2024050114-CVE-2024-27048-016f@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit a96202a ("wifi: brcmfmac: cfg80211: Add support
for PMKID_V3 operations") in v6.4-rc1.
This commit was not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [b4152222e04cb8afeeca239c90e3fcaf4c553b42]
stable/6.6: [df62e22c2e27420e8990a4f09e30d7bf56c2036f]
stable/6.8: [6138a82f3bccfc67ed7ac059493579fc326c02e5]

CVE-2024-27049: wifi: mt76: mt7925e: fix use-after-free in free_irq()

Announce: https://lore.kernel.org/linux-cve-announce/2024050114-CVE-2024-27049-a5a1@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit c948b5d ("wifi: mt76: mt7925: add Mediatek Wi-Fi7
driver for mt7925 chips") in v6.7-rc1.
This commit was not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [a5a5f4413d91f395cb2d89829d376d7393ad48b9]
stable/6.8: [6d9930096e1f13cf6d9aabfbf95d0e05fb04144f]

CVE-2024-27050: libbpf: Use OPTS_SET() macro in bpf_xdp_query()

Announce: https://lore.kernel.org/linux-cve-announce/2024050114-CVE-2024-27050-b829@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 13ce2da ("xsk: add new netlink attribute
dedicated for ZC max frags") in v6.6-rc1.
This commit was not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [92a871ab9fa59a74d013bc04f321026a057618e7]
stable/6.6: [fa5bef5e80c6a3321b2b1a7070436f3bc5daf07c]
stable/6.8: [cd3be9843247edb8fc6fcd8d8237cbce2bc19f5e]

CVE-2024-27051: cpufreq: brcmstb-avs-cpufreq: add check for
cpufreq_cpu_get's return value

Announce: https://lore.kernel.org/linux-cve-announce/2024050114-CVE-2024-27051-07ce@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit de322e0 ("cpufreq: brcmstb-avs-cpufreq: AVS
CPUfreq driver for Broadcom STB SoCs") in v4.10-rc1.
This commit was not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [f661017e6d326ee187db24194cabb013d81bc2a6]
stable/5.10: [9127599c075caff234359950117018a010dd01db]
stable/5.15: [d951cf510fb0df91d3abac0121a59ebbc63c0567]
stable/6.1: [e72160cb6e23b78b41999d6885a34ce8db536095]
stable/6.6: [b25b64a241d769e932a022e5c780cf135ef56035]
stable/6.8: [e6e3e51ffba0784782b1a076d7441605697ea3c6]

CVE-2024-27052: wifi: rtl8xxxu: add cancel_work_sync() for c2hcmd_work

Announce: https://lore.kernel.org/linux-cve-announce/2024050115-CVE-2024-27052-fb6d@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit e542e66 ("rtl8xxxu: add bluetooth co-existence
support for single antenna") in v5.5-rc1.
This commit was not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [1213acb478a7181cd73eeaf00db430f1e45b1361]
stable/5.10: [dddedfa3b29a63c2ca4336663806a6128b8545b4]
stable/5.15: [ac512507ac89c01ed6cd4ca53032f52cdb23ea59]
stable/6.1: [3518cea837de4d106efa84ddac18a07b6de1384e]
stable/6.6: [156012667b85ca7305cb363790d3ae8519a6f41e]
stable/6.8: [58fe3bbddfec10c6b216096d8c0e517cd8463e3a]

CVE-2024-27053: wifi: wilc1000: fix RCU usage in connect path

Announce: https://lore.kernel.org/linux-cve-announce/2024050115-CVE-2024-27053-a8e9@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit c460495 ("staging: wilc1000: fix incorrent type
in initializer") in v5.1-rc1.
This commit was not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [205c50306acf58a335eb19fa84e40140f4fe814f]
stable/5.10: [b4bbf38c350acb6500cbe667b1e2e68f896e4b38]
stable/5.15: [d80fc436751cfa6b02a8eda74eb6cce7dadfe5a2]
stable/5.4: [e556006de4ea93abe2b46cba202a2556c544b8b2]
stable/6.1: [745003b5917b610352f52fe0d11ef658d6471ec2]
stable/6.6: [4bfd20d5f5c62b5495d6c0016ee6933bd3add7ce]
stable/6.8: [dd50d3ead6e3707bb0a5df7cc832730c93ace3a7]

CVE-2024-27054: s390/dasd: fix double module refcount decrement

Announce: https://lore.kernel.org/linux-cve-announce/2024050115-CVE-2024-27054-b0ff@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit c020d72 ("s390/dasd: fix panic during offline
processing") in v4.9-rc1.
This commit was not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [c3116e62ddeff79cae342147753ce596f01fcf06]
stable/5.15: [edbdb0d94143db46edd373cc93e433832d29fe19]
stable/6.1: [ad999aa18103fa038787b6a8a55020abcf34df1a]
stable/6.6: [ec09bcab32fc4765e0cc97e1b72cdd067135f37e]
stable/6.8: [ebc5a3bd79e54f98c885c26f0862a27a02c487c5]

CVE-2024-27055: workqueue: Don't call cpumask_test_cpu() with -1 CPU
in wq_update_node_max_active()

Announce: https://lore.kernel.org/linux-cve-announce/2024050115-CVE-2024-27055-449e@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 5797b1c ("workqueue: Implement system-wide
nr_active enforcement for unbound workqueues") in 6.9-rc1.
This commit was backported to 6.6 and 6.8.
Fixed in 6.9-rc1.

Fixed status
mainline: [15930da42f8981dc42c19038042947b475b19f47]
stable/6.6: [7df62b8cca38aa452b508b477b16544cba615084]
stable/6.8: [a75ac2693d734d20724f0e10e039ca85f1fcfc4e]

CVE-2024-27056: wifi: iwlwifi: mvm: ensure offloading TID queue exists

Announce: https://lore.kernel.org/linux-cve-announce/2024050115-CVE-2024-27056-98c0@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc7.

Fixed status
mainline: [78f65fbf421a61894c14a1b91fe2fb4437b3fe5f]

CVE-2024-27057: ASoC: SOF: ipc4-pcm: Workaround for crashed firmware
on system suspend

Announce: https://lore.kernel.org/linux-cve-announce/2024050116-CVE-2024-27057-c0fb@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc5.
It seems as if it was introduced by commit 2d271af ("ASoC: SOF:
ipc4-pcm: Use the PCM stream's pipeline_info during trigger") in
6.3-rc1.
This commit is not backported to older stable kernels.

Fixed status
mainline: [c40aad7c81e5fba34b70123ed7ce3397fa62a4d2]
stable/6.6: [3cac6eebea9b4bc5f041e157e45c76e212ad6759]

CVE-2024-27058: tmpfs: fix race on handling dquot rbtree

Announce: https://lore.kernel.org/linux-cve-announce/2024050130-CVE-2024-27058-e8f6@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit eafc474 ("shmem: prepare shmem quota
infrastructure") in v6.6-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc2.

Fixed status
mainline: [0a69b6b3a026543bc215ccc866d0aea5579e6ce2]
stable/6.6: [c7077f43f30d817d10a9f8245e51576ac114b2f0]
stable/6.8: [f82f184874d2761ebaa60dccf577921a0dbb3810]

CVE-2024-27059: USB: usb-storage: Prevent divide-by-0 error in
isd200_ata_command

Announce: https://lore.kernel.org/linux-cve-announce/2024050130-CVE-2024-27059-baaa@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 1da177e ("Linux-2.6.12-rc2") in v2.6.12.
Fixed in v6.8.

Fixed status
cip/4.4: [3b252232c2204c18e7c75b33f1c3725cf9239512]
cip/4.4-st: [3b252232c2204c18e7c75b33f1c3725cf9239512]
mainline: [014bcf41d946b36a8f0b8e9b5d9529efbb822f49]
stable/4.19: [9968c701cba7eda42e5f0052b040349d6222ae34]
stable/5.10: [284fb1003d5da111019b9e0bf99b084fd71ac133]
stable/5.15: [6c1f36d92c0a8799569055012665d2bb066fb964]
stable/5.4: [eb7b01ca778170654e1c76950024270ba74b121f]
stable/6.1: [f42ba916689f5c7b1642092266d2f53cf527aaaa]
stable/6.6: [871fd7b10b56d280990b7e754f43d888382ca325]
stable/6.8: [014bcf41d946b36a8f0b8e9b5d9529efbb822f49]

CVE-2024-27060: thunderbolt: Fix NULL pointer dereference in
tb_port_update_credits()

Announce: https://lore.kernel.org/linux-cve-announce/2024050130-CVE-2024-27060-8a1c@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 81af295 ("thunderbolt: Add support for asymmetric
link") in v6.7-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8.

Fixed status
mainline: [d3d17e23d1a0d1f959b4fa55b35f1802d9c584fa]
stable/6.8: [d3d17e23d1a0d1f959b4fa55b35f1802d9c584fa]

CVE-2024-27061: crypto: sun8i-ce - Fix use after free in unprepare

Announce: https://lore.kernel.org/linux-cve-announce/2024050130-CVE-2024-27061-fef2@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 4136212 ("crypto: sun8i-ce - Remove
prepare/unprepare request") in v6.6-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8.

Fixed status
mainline: [183420038444547c149a0fc5f58e792c2752860c]
stable/6.6: [dc60b25540c82fc4baa95d1458ae96ead21859e0]
stable/6.8: [183420038444547c149a0fc5f58e792c2752860c]

CVE-2024-27062: nouveau: lock the client object tree.

Announce: https://lore.kernel.org/linux-cve-announce/2024050130-CVE-2024-27062-3291@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8.
It looks as if commit 110cccf ("drm/nouveau/core/object: support
lookup of specific object types") in 4.11-rc1 introduced this bug.
Linux 4.4 doesn't have vulnerable functions.

Fixed status
mainline: [b7cc4ff787a572edf2c55caeffaa88cd801eb135]
stable/6.6: [6887314f5356389fc219b8152e951ac084a10ef7]
stable/6.8: [b7cc4ff787a572edf2c55caeffaa88cd801eb135]

CVE-2024-27063: leds: trigger: netdev: Fix kernel panic on interface
rename trig notify

Announce: https://lore.kernel.org/linux-cve-announce/2024050131-CVE-2024-27063-c356@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit d5e0126 ("leds: trigger: netdev: add additional
specific link speed mode") in v6.5-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [415798bc07dd1c1ae3a656aa026580816e0b9fe8]
stable/6.6: [10f2af1af8ab8a7064f193446abd5579d3def7e3]
stable/6.8: [3f360227cb46edb2cd2494128e1e06ed5768a62e]

CVE-2024-27064: netfilter: nf_tables: Fix a memory leak in nf_tables_updchain

Announce: https://lore.kernel.org/linux-cve-announce/2024050132-CVE-2024-27064-8046@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit b9703ed ("netfilter: nf_tables: support for
adding new devices to an existing netdev chain") in v6.4-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [7eaf837a4eb5f74561e2486972e7f5184b613f6e]
stable/6.6: [79846fdcc548d617b0b321addc6a3821d3b75b20]
stable/6.8: [e77a6b53a3a547b6dedfc40c37cee4f310701090]

CVE-2024-27065: netfilter: nf_tables: do not compare internal table
flags on updates

Announce: https://lore.kernel.org/linux-cve-announce/2024050132-CVE-2024-27065-8c9d@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 179d9ba ("netfilter: nf_tables: fix table flag
updates") in v5.13-rc5.
This commit was backported to 5.10 and 5.4.
Fixed in v6.9-rc1.

Fixed status
mainline: [4a0e7f2decbf9bd72461226f1f5f7dcc4b08f139]
stable/5.10: [fcf32a5bfcb8a57ac0ce717fcfa4d688c91f1005]
stable/5.15: [640dbf688ba955e83e03de84fbdda8e570b7cce4]
stable/5.4: [2531f907d3e40a6173090f10670ae76d117ab27b]
stable/6.1: [9683cb6c2c6c0f45537bf0b8868b5d38fcb63fc7]
stable/6.6: [4d37f12707ee965d338028732575f0b85f6d9e4f]
stable/6.8: [df257c435e51651c43b86326d112ddadda76350e]

CVE-2024-27066: virtio: packed: fix unmap leak for indirect desc table

Announce: https://lore.kernel.org/linux-cve-announce/2024050132-CVE-2024-27066-686a@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit b319940 ("virtio_ring: skip unmap for premapped")
in v6.6-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [d5c0ed17fea60cca9bc3bf1278b49ba79242bbcd]
stable/6.6: [e142169aca5546ae6619c39a575cda8105362100]
stable/6.8: [51bacd9d29bf98c3ebc65e4a0477bb86306b4140]

CVE-2024-27067: xen/evtchn: avoid WARN() when unbinding an event channel

Announce: https://lore.kernel.org/linux-cve-announce/2024050132-CVE-2024-27067-38e7@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 9e90e58 ("xen: evtchn: Allow shared registration
of IRQ handers") in v6.7-rc1.
This commit is backported to 6.6.
Fixed in v6.9-rc1.

Fixed status
mainline: [51c23bd691c0f1fb95b29731c356c6fd69925d17]
stable/6.6: [99e425032c6ec13584d3cd33846e0c7307501b47]
stable/6.8: [9e2d4b58c1da48a32905802aaeadba7084b46895]

CVE-2024-27068: thermal/drivers/mediatek/lvts_thermal: Fix a memory
leak in an error handling path

Announce: https://lore.kernel.org/linux-cve-announce/2024050132-CVE-2024-27068-c844@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit f5f633b ("thermal/drivers/mediatek: Add the Low
Voltage Thermal Sensor driver") in v6.3-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [ca93bf607a44c1f009283dac4af7df0d9ae5e357]
stable/6.6: [2db869da91afd48e5b9ec76814709be49662b07d]
stable/6.8: [9b02197596671800dd934609384b1aca7c6ad218]

CVE-2024-27069: ovl: relax WARN_ON in ovl_verify_area()

Announce: https://lore.kernel.org/linux-cve-announce/2024050133-CVE-2024-27069-5b70@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit ca7ab48 ("ovl: add permission hooks outside of
do_splice_direct()") in v6.8-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [77a28aa476873048024ad56daf8f4f17d58ee48e]
stable/6.8: [c3c85aefc0da1e5074a06c682542a54ccc99bdca]

CVE-2024-27070: f2fs: fix to avoid use-after-free issue in f2fs_filemap_fault

Announce: https://lore.kernel.org/linux-cve-announce/2024050133-CVE-2024-27070-a43e@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 87f3afd ("f2fs: add tracepoint for
f2fs_vm_page_mkwrite()") in v6.8-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [eb70d5a6c932d9d23f4bb3e7b83782c21ac4b064]
stable/6.8: [8186e16a766d709a08f188d2f4e84098f364bea1]

CVE-2024-27071: backlight: hx8357: Fix potential NULL pointer dereference

Announce: https://lore.kernel.org/linux-cve-announce/2024050133-CVE-2024-27071-3b1b@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 7d84a63 ("backlight: hx8357: Convert to agnostic
GPIO API") in v6.8-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [b1ba8bcb2d1ffce11b308ce166c9cc28d989e3b9]
stable/6.8: [67e578c8ff2d7df03bf8ca9a7f5436b1796f6ad1]

CVE-2024-27072: media: usbtv: Remove useless locks in usbtv_video_free()

Announce: https://lore.kernel.org/linux-cve-announce/2024050133-CVE-2024-27072-301d@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit c838530 ("media: media videobuf2: Be more
flexible on the number of queue stored buffers") in v6.8-rc1.
Introduced by commit f3d27f3 ("[media] usbtv: Add driver for Fushicai
USBTV007 video frame grabber") in v3.11-rc1.
Fixed in v6.9-rc1.

Fixed status
mainline: [65e6a2773d655172143cc0b927cdc89549842895]
stable/6.8: [3e7d82ebb86e94643bdb30b0b5b077ed27dce1c2]

CVE-2024-27073: media: ttpci: fix two memleaks in budget_av_attach

Announce: https://lore.kernel.org/linux-cve-announce/2024050133-CVE-2024-27073-967c@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 1da177e ("Linux-2.6.12-rc2") in v2.6.12.
Fixed in v6.9-rc1.

Fixed status
mainline: [d0b07f712bf61e1a3cf23c87c663791c42e50837]
stable/5.10: [910363473e4bf97da3c350e08d915546dd6cc30b]
stable/5.15: [24e51d6eb578b82ff292927f14b9f5ec05a46beb]
stable/5.4: [af37aed04997e644f7e1b52b696b62dcae3cc016]
stable/6.1: [55ca0c7eae8499bb96f4e5d9b26af95e89c4e6a0]
stable/6.6: [7393c681f9aa05ffe2385e8716989565eed2fe06]
stable/6.8: [656b8cc123d7635dd399d9f02594f27aa797ac3c]

CVE-2024-27074: media: go7007: fix a memleak in go7007_load_encoder

Announce: https://lore.kernel.org/linux-cve-announce/2024050133-CVE-2024-27074-a9b3@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 95ef394 ("[media] go7007: remember boot
firmware") in v3.10-rc1.
Fixed in v6.9-rc1.

Fixed status
cip/4.4: [01173c381edc48d33487a9f6a1e306ed41fda472]
cip/4.4-st: [01173c381edc48d33487a9f6a1e306ed41fda472]
mainline: [b9b683844b01d171a72b9c0419a2d760d946ee12]
stable/4.19: [7f11dd3d165b178e738fe73dfeea513e383bedb5]
stable/5.10: [b49fe84c6cefcc1c2336d793b53442e716c95073]
stable/5.15: [790fa2c04dfb9f095ec372bf17909424d6e864b3]
stable/5.4: [291cda0b805fc0d6e90d201710311630c8667159]
stable/6.1: [e04d15c8bb3e111dd69f98894acd92d63e87aac3]
stable/6.6: [f31c1cc37411f5f7bcb266133f9a7e1b4bdf2975]
stable/6.8: [7405a0d4442792988e9ae834e7d84f9d163731a4]

CVE-2024-27075: media: dvb-frontends: avoid stack overflow warnings with clang

Announce: https://lore.kernel.org/linux-cve-announce/2024050134-CVE-2024-27075-5e4f@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 3cd890d ("media: dvb-frontends: fix i2c access
helpers for KASAN") in v4.16-rc1.
This commit was backported to 4.4
Fixed in v6.9-rc1.

Fixed status
mainline: [7a4cf27d1f0538f779bf31b8c99eda394e277119]
stable/4.19: [c073c8cede5abd3836e83d70d72606d11d0759d4]
stable/5.10: [fb07104a02e87c06c39914d13ed67fd8f839ca82]
stable/5.15: [d20b64f156de5d10410963fe238d82a4e7e97a2f]
stable/5.4: [fa8b472952ef46eb632825051078c21ce0cafe55]
stable/6.1: [107052a8cfeff3a97326277192b4f052e4860a8a]
stable/6.6: [8fad9c5bb00d3a9508d18bbfe832e33a47377730]
stable/6.8: [ed514ecf4f29c80a2f09ae3c877059b401efe893]

CVE-2024-27076: media: imx: csc/scaler: fix v4l2_ctrl_handler memory leak

Announce: https://lore.kernel.org/linux-cve-announce/2024050134-CVE-2024-27076-5a2e@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit a8ef048 ("media: imx: add csc/scaler mem2mem
device") in v5.4-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [4797a3dd46f220e6d83daf54d70c5b33db6deb01]
stable/5.10: [5d9fe604bf9b5b09d2215225df55f22a4cbbc684]
stable/5.15: [b1d0eebaf87cc9ccd05f779ec4a0589f95d6c18b]
stable/5.4: [8c2e4efe1278cd2b230cdbf90a6cefbf00acc282]
stable/6.1: [8df9a3c7044b847e9c4dc7e683fd64c6b873f328]
stable/6.6: [d164ddc21e986dd9ad614b4b01746e5457aeb24f]
stable/6.8: [6c92224721a439d6350db5933a1060768dcd565e]

CVE-2024-27077: media: v4l2-mem2mem: fix a memleak in v4l2_m2m_register_entity

Announce: https://lore.kernel.org/linux-cve-announce/2024050134-CVE-2024-27077-3482@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit be2fff6 ("media: add helpers for memory-to-memory
media controller") in v4.19-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [8f94b49a5b5d386c038e355bef6347298aabd211]
stable/4.19: [3dd8abb0ed0e0a7c66d6d677c86ccb188cc39333]
stable/5.10: [afd2a82fe300032f63f8be5d6cd6981e75f8bbf2]
stable/5.15: [dc866b69cc51af9b8509b4731b8ce2a4950cd0ef]
stable/5.4: [0175f2d34c85744f9ad6554f696cf0afb5bd04e4]
stable/6.1: [0c9550b032de48d6a7fa6a4ddc09699d64d9300d]
stable/6.6: [90029b9c979b60de5cb2b70ade4bbf61d561bc5d]
stable/6.8: [9c23ef30e840fedc66948299509f6c2777c9cf4f]

CVE-2024-27078: media: v4l2-tpg: fix some memleaks in tpg_alloc

Announce: https://lore.kernel.org/linux-cve-announce/2024050134-CVE-2024-27078-6a54@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 63881df ("[media] vivid: add the Test Pattern
Generator") in v3.18-rc1.
Fixed in v6.9-rc1.

Fixed status
mainline: [8cf9c5051076e0eb958f4361d50d8b0c3ee6691c]
stable/4.19: [0de691ff547d86dd54c24b40a81f9c925df8dd77]
stable/5.10: [94303a06e1852a366e9671fff46d19459f88cb28]
stable/5.15: [770a57922ce36a8476c43f7400b6501c554ea511]
stable/5.4: [8269ab16415f2065cd792c49b0475543936cbd79]
stable/6.1: [6bf5c2fade8ed53b2d26fa9875e5b04f36c7145d]
stable/6.6: [4c86c772fef06f5d7a66151bac42366825db0941]
stable/6.8: [622b1cf38521569869c8f7b9fbe9e4f1a289add7]

CVE-2024-27079: iommu/vt-d: Fix NULL domain on device release

Announce: https://lore.kernel.org/linux-cve-announce/2024050134-CVE-2024-27079-f478@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 586081d ("iommu/vt-d: Remove
DEFER_DEVICE_DOMAIN_INFO") in v5.18-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [81e921fd321614c2ad8ac333b041aae1da7a1c6d]
stable/6.8: [333fe86968482ca701c609af590003bcea450e8f]

CVE-2024-27080: btrfs: fix race when detecting delalloc ranges during fiemap

Announce: https://lore.kernel.org/linux-cve-announce/2024050135-CVE-2024-27080-46f0@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit b0ad381 ("btrfs: fix deadlock with fiemap and
extent locking") in v6.8-rc6.
This commit was backported to 6.6.
Fixed in v6.9-rc1.

Fixed status
mainline: [978b63f7464abcfd364a6c95f734282c50f3decf]
stable/6.6: [49d640d2946c35a17b051d54171a032dd95b0f50]
stable/6.8: [ced63fffd63072c0ca55d5a451010d71bf08c0b3]

CVE-2024-27388: SUNRPC: fix some memleaks in gssx_dec_option_array

Announce: https://lore.kernel.org/linux-cve-announce/2024050135-CVE-2024-27388-04eb@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 1d65833 ("SUNRPC: Add RPC based upcall mechanism
for RPCGSS auth") in v3.10-rc1.
Fixed in v6.9-rc1.

Fixed status
cip/4.4: [fd2507f998926b304ebe36d812747858526148b9]
cip/4.4-st: [fd2507f998926b304ebe36d812747858526148b9]
mainline: [3cfcfc102a5e57b021b786a755a38935e357797d]
stable/4.19: [b97c37978ca825557d331c9012e0c1ddc0e42364]
stable/5.10: [bb336cd8d5ecb69c430ebe3e7bcff68471d93fa8]
stable/5.15: [dd292e884c649f9b1c18af0ec75ca90b390cd044]
stable/5.4: [bfa9d86d39a0fe4685f90c3529aa9bd62a9d97a8]
stable/6.1: [934212a623cbab851848b6de377eb476718c3e4c]
stable/6.6: [5e6013ae2c8d420faea553d363935f65badd32c3]
stable/6.8: [996997d1fb2126feda550d6adcedcbd94911fc69]

CVE-2024-27389: pstore: inode: Only d_invalidate() is needed

Announce: https://lore.kernel.org/linux-cve-announce/2024050135-CVE-2024-27389-fb3a@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 609e28b ("pstore: Remove filesystem records when
backend is unregistered") in v5.8-rc1.
This commit was not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [a43e0fc5e9134a46515de2f2f8d4100b74e50de3]
stable/6.1: [db6e5e16f1ee9e3b01d2f71c7f0ba945f4bf0f4e]
stable/6.6: [4cdf9006fc095af71da80e9b5f48a32e991b9ed3]
stable/6.8: [340682ed1932b8e3bd0bfc6c31a0c6354eb57cc6]

CVE-2024-27390: ipv6: mcast: remove one synchronize_net() barrier in
ipv6_mc_down()

Announce: https://lore.kernel.org/linux-cve-announce/2024050135-CVE-2024-27390-e55f@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit f185de2 ("mld: add new workqueues for process mld
events") in v5.13-rc1.
This commit was not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [17ef8efc00b34918b966388b2af0993811895a8c]
stable/5.15: [9d159d6637ccce25f879d662a480541ef4ba3a50]
stable/6.1: [a03ede2282ebbd181bd6f5c38cbfcb5765afcd04]
stable/6.6: [26d4bac55750d535f1f0b8790dc26daf6089e373]
stable/6.8: [5da9a218340a2bc804dc4327e5804392e24a0b88]

CVE-2024-27391: wifi: wilc1000: do not realloc workqueue everytime an
interface is added

Announce: https://lore.kernel.org/linux-cve-announce/2024050135-CVE-2024-27391-6014@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 09ed8bf ("wilc1000: Rename workqueue from
"WILC_wq" to "NETDEV-wq"") in v5.17-rc1.
This commit was not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [328efda22af81130c2ad981c110518cb29ff2f1d]
stable/6.1: [515cc676dfbce40d93c92b1ff3c1070e917f4e52]
stable/6.6: [4041c60a9d543b3ad50225385b072ba68e96166e]
stable/6.8: [9ab0c303ccabfd6bdce14432792d41090070008c]

CVE-2024-27392: nvme: host: fix double-free of struct nvme_id_ns in
ns_update_nuse()

Announce: https://lore.kernel.org/linux-cve-announce/2024050136-CVE-2024-27392-b84b@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit a1a825a ("nvme: add csi, ms and nuse to sysfs")
in v6.8-rc1.
This commit was not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [8d0d2447394b13fb22a069f0330f9c49b7fff9d3]
stable/6.8: [534f9dc7fe495b3f9cc84363898ac50c5a25fccb]

* Updated CVEs

CVE-2024-26605: PCI/ASPM: Fix deadlock when enabling ASPM

stable 6.1 and 6.6 were fixed.

Fixed status
mainline: [1e560864159d002b453da42bd2c13a1805515a20]
stable/6.1: [0f7908a016c092cfdaa16d785fa5099d867bc1a3]
stable/6.6: [b0f4478838be1f1d330061201898fef65bf8fd7c]
stable/6.7: [ef90508574d7af48420bdc5f7b9a4f1cdd26bc70]

CVE-2024-26811: ksmbd: validate payload size in ipc response

stable 5.15 was fixed.

Fixed status
mainline: [a677ebd8ca2f2632ccdecbad7b87641274e15aac]
stable/5.15: [88b7f1143b15b29cccb8392b4f38e75b7bb3e300]
stable/6.1: [51a6c2af9d20203ddeeaf73314ba8854b38d01bd]
stable/6.6: [a637fabac554270a851033f5ab402ecb90bc479c]
stable/6.8: [76af689a45aa44714b46d1a7de4ffdf851ded896]

CVE-2024-26922: drm/amdgpu: validate the parameters of bo mapping
operations more clearly

stable 5.15, 6.1, 6.6, and 6.8 were fixed.

Fixed status
mainline: [6fef2d4c00b5b8561ad68dd2b68173f5c6af1e75]
stable/5.15: [8b12fc7b032633539acdf7864888b0ebd49e90f2]
stable/6.1: [212e3baccdb1939606420d88f7f52d346b49a284]
stable/6.6: [ef13eeca7c79136bc38e21eb67322c1cbd5c40ee]
stable/6.8: [b1f04b9b1c5317f562a455384c5f7473e46bdbaa]

CVE-2024-26924: netfilter: nft_set_pipapo: do not free live element

stable 5.15, 6.1, 6.6, and 6.8 were fixed.

Fixed status
mainline: [3cfc9ec039af60dbd8965ae085b2c2ccdcfbe1cc]
stable/5.15: [7a1679e2d9bfa3b5f8755c2c7113e54b7d42bd46]
stable/6.1: [41d8fdf3afaff312e17466e4ab732937738d5644]
stable/6.6: [ebf7c9746f073035ee26209e38c3a1170f7b349a]
stable/6.8: [14b001ba221136c15f894577253e8db535b99487]

CVE-2024-26926: binder: check offset alignment in binder_get_object()

stable 5.15, 6.1, 6.6, and 6.8 were fixed.

Fixed status
mainline: [aaef73821a3b0194a01bd23ca77774f704a04d40]
stable/5.15: [a2fd6dbc98be1105a1d8e9e31575da8873ef115c]
stable/6.1: [a6d2a8b211c874971ee4cf3ddd167408177f6e76]
stable/6.6: [1d7f1049035b2060342f11eff957cf567d810bdc]
stable/6.8: [f01d6619045704d78613b14e2e0420bfdb7f1c15]

Currently tracking CVEs

CVE-2021-31615: Unencrypted Bluetooth Low Energy baseband links in
Bluetooth Core Specifications 4.0 through 5.2

There is no fix information.

CVE-2020-26556: kernel: malleable commitment Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26557: kernel: predictable Authvalue in Bluetooth Mesh
Provisioning Leads to MITM

No fix information.

CVE-2020-26559: kernel: Authvalue leak in Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26560: kernel: impersonation attack in Bluetooth Mesh Provisioning

No fix information.

Regards,
-- 
Masami Ichikawa
Cybertrust Japan Co., Ltd.

Email :masami.ichikawa@cybertrust.co.jp
          :masami.ichikawa@miraclelinux.com


^ permalink raw reply	[flat|nested] 33+ messages in thread

* [kernel-cve-report] New CVE entries this week
@ 2024-04-24 22:53 Masami Ichikawa
  0 siblings, 0 replies; 33+ messages in thread
From: Masami Ichikawa @ 2024-04-24 22:53 UTC (permalink / raw)
  To: cip-dev

Hi!

It's this week's CVE report.

This week reported 10 new CVEs and 6 updated CVEs.

* New CVEs

CVE-2024-26921: inet: inet_defrag: prevent sk release while still in use

Announce: https://lore.kernel.org/linux-cve-announce/2024041819-CVE-2024-26921-e3b3@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 7026b1d ("netfilter: Pass socket pointer down
through okfn().") in v4.1-rc1.
Fixed in v6.9-rc2.

Fixed status
mainline: [18685451fc4e546fc0e718580d32df3c0e5c8272]
stable/6.1: [7d0567842b78390dd9b60f00f1d8f838d540e325]
stable/6.6: [f4877225313d474659ee53150ccc3d553a978727]
stable/6.8: [e09cbe017311508c21e0739e97198a8388b98981]

CVE-2024-24856: Missing null pointer check causes a null pointer dereference bug

Announce: https://www.cve.org/CVERecord?id=CVE-2024-24856
CVSS v3(NIST): N/A
CVSS v3(CNA): 5.3 MEDIUM

The memory allocation function ACPI_ALLOCATE_ZEROED does not guarantee
a successful allocation,
but the subsequent code directly dereferences the pointer that
receives it, which may lead to null pointer dereference.
To fix this issue, a null pointer check should be added. If it is
null, return exception code AE_NO_MEMORY.

Fixed status
Not fixed yet.

CVE-2024-24862: Null pointer dereference bug in pci1xxxx_spi_probe()

Announce: https://www.cve.org/CVERecord?id=CVE-2024-24862
CVSS v3(NIST): N/A
CVSS v3(CNA): 5.3 MEDIUM

In function pci1xxxx_spi_probe, there is a potential null pointer that
may be caused by a failed memory allocation
by the function devm_kzalloc. Hence, a null pointer check needs to be
added to prevent null pointer dereferencing
later in the code. To fix this issue, spi_bus->spi_int[iter] should be
checked. The memory allocated by
devm_kzalloc will be automatically released, so just directly return
-ENOMEM without worrying about memory leaks.

It report said that it affected from v6.2 before v6.9-rc3

Fixed status
Not fixed yet.

CVE-2024-24863: Null pointer dereference bug in malidp_mw_connector_reset()

Announce: https://www.cve.org/CVERecord?id=CVE-2024-24863
CVSS v3(NIST): N/A
CVSS v3(CNA): 5.3 MEDIUM

In malidp_mw_connector_reset, new memory is allocated with kzalloc,
but no check is performed. In order to prevent null pointer
dereferencing, ensure that mw_state is checked before calling
__drm_atomic_helper_connector_reset.

It report said that it affected from v4.19-rc1 before v6.9-rc2

Fixed status
Not fixed yet.

CVE-2024-24891: Kernel information leak in tcm.c

Announce: https://www.cve.org/CVERecord?id=CVE-2024-24891
CVSS v3(NIST): N/A
CVSS v3(CNA): 6.0 MEDIUM

Exposure of Sensitive Information to an Unauthorized Actor
vulnerability in openEuler kernel on Linux allows Resource
Leak Exposure. This vulnerability is associated with program files
https://gitee.Com/openeuler/kernel/blob/openEuler-1.0-LTS/drivers/staging/gmjstcm/tcm.C.
This issue affects kernel: from 4.19.90-2109.1.0.0108 before
4.19.90-2403.4.0.0244.

The drivers/staging/gmjstcm/tcm.c is not found in the mainline so we
do not have to take care of this CVE.

Fixed status
This bug is not in the mainline nor stable kernels.

CVE-2024-24898: Kernel information leak in tcm.c

Announce: https://www.cve.org/CVERecord?id=CVE-2024-24898
CVSS v3(NIST): N/A
CVSS v3(CNA): 6.0 MEDIUM

Exposure of Sensitive Information to an Unauthorized Actor
vulnerability in openEuler kernel on Linux allows
Resource Leak Exposure. This vulnerability is associated with program files
https://gitee.Com/openeuler/kernel/blob/openEuler-1.0-LTS/drivers/staging/gmjstcm/tcm.C.
This issue affects kernel: from 4.19.90-2109.1.0.0108 before
4.19.90-2403.4.0.0244.

The drivers/staging/gmjstcm/tcm.c is not found in the mainline so we
do not have to take care of this CVE.

Fixed status
This bug is not in the mainline nor stable kernels.

CVE-2024-26922: drm/amdgpu: validate the parameters of bo mapping
operations more clearly

Announce: https://lore.kernel.org/linux-cve-announce/2024042317-CVE-2024-26922-896d@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit dc54d3d ("drm/amdgpu: implement
AMDGPU_VA_OP_CLEAR v2") in v4.12-rc1.
Linux 4.4 is not affected.
Fixed in v6.9-rc5.

Fixed status
mainline: [6fef2d4c00b5b8561ad68dd2b68173f5c6af1e75]

CVE-2024-26923: af_unix: Fix garbage collector racing against connect()

Announce: https://lore.kernel.org/linux-cve-announce/2024042418-CVE-2024-26923-f7f6@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 1fd05ba ("[AF_UNIX]: Rewrite garbage collector,
fixes race.") in v2.6.23-rc1.
Fixed in v6.9-rc4.

Fixed status
mainline: [47d8ac011fe1c9251070e1bd64cb10b48193ec51]
stable/5.15: [e76c2678228f6aec74b305ae30c9374cc2f28a51]
stable/6.1: [b75722be422c276b699200de90527d01c602ea7c]
stable/6.6: [507cc232ffe53a352847893f8177d276c3b532a9]
stable/6.8: [dbdf7bec5c920200077d693193f989cb1513f009]

CVE-2024-26924: netfilter: nft_set_pipapo: do not free live element

Announce: https://lore.kernel.org/linux-cve-announce/2024042420-CVE-2024-26924-4d1e@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 3c4287f ("nf_tables: Add set type for arbitrary
concatenation of ranges") in v5.6-rc1.
This commit is not backported to 5.4, 4.19, and 4.4.
Fixed in v6.9-rc5.

Fixed status
mainline: [3cfc9ec039af60dbd8965ae085b2c2ccdcfbe1cc]

CVE-2024-26925: netfilter: nf_tables: release mutex after
nft_gc_seq_end from abort path

Announce: https://lore.kernel.org/linux-cve-announce/2024042421-CVE-2024-26925-7c19@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 7203443 ("netfilter: nf_tables: GC transaction
race with abort path") in v6.5.
This commit was backported to 5.10, 5.15, 5.4, and 6.1. Linux 4.x is
not affected.
Fixed in v6.9-rc3.

Fixed status
mainline: [0d459e2ffb541841714839e8228b845458ed3b27]
stable/5.10: [2cee2ff7f8cce12a63a0a23ffe27f08d99541494]
stable/5.15: [eb769ff4e281f751adcaf4f4445cbf30817be139]
stable/5.4: [61ac7284346c32f9a8c8ceac56102f7914060428]
stable/6.1: [8d3a58af50e46167b6f1db47adadad03c0045dae]
stable/6.6: [8038ee3c3e5b59bcd78467686db5270c68544e30]
stable/6.8: [a34ba4bdeec0c3b629160497594908dc820110f1]

* Updated CVEs

CVE-2022-38096: drm/vmwgfx: Fix possible null pointer derefence with
invalid contexts

The mainlinx, 5.10, 5.15, 6.1, 6.6, and 6.8 were fixed.

Fixed status
mainline: [517621b7060096e48e42f545fa6646fc00252eac]
stable/5.10: [c560327d900bab968c2e1b4cd7fa2d46cd429e3d]
stable/5.15: [899e154f9546fcae18065d74064889d08fff62c2]
stable/6.1: [07c3fe923ff7eccf684fb4f8c953d0a7cc8ded73]
stable/6.6: [ff41e0d4f3fa10d7cdd7d40f8026bea9fcc8b000]
stable/6.8: [585fec7361e7850bead21fada49a7fcde2f2e791]

Currently tracking CVEs

CVE-2021-31615: Unencrypted Bluetooth Low Energy baseband links in
Bluetooth Core Specifications 4.0 through 5.2

There is no fix information.

CVE-2020-26556: kernel: malleable commitment Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26557: kernel: predictable Authvalue in Bluetooth Mesh
Provisioning Leads to MITM

No fix information.

CVE-2020-26559: kernel: Authvalue leak in Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26560: kernel: impersonation attack in Bluetooth Mesh Provisioning

No fix information.

Regards,
-- 
Masami Ichikawa
Cybertrust Japan Co., Ltd.

Email :masami.ichikawa@cybertrust.co.jp
          :masami.ichikawa@miraclelinux.com


^ permalink raw reply	[flat|nested] 33+ messages in thread

* [kernel-cve-report] New CVE entries this week
@ 2024-04-18  4:09 Masami Ichikawa
  0 siblings, 0 replies; 33+ messages in thread
From: Masami Ichikawa @ 2024-04-18  4:09 UTC (permalink / raw)
  To: cip-dev

Hi!

It's this week's CVE report.

This week reported 108 new CVEs and 27 updated CVEs.

* New CVEs

CVE-2024-26817: amdkfd: use calloc instead of kzalloc to avoid integer overflow

Announce: https://lore.kernel.org/linux-cve-announce/2024041311-CVE-2024-26817-e1a0@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit is not determined. Fixed in master branch.
It looks as if this bug was introduced by commit c7bcbfa4f
("drm/amdkfd: Remove limit on number of GPUs") in 4.17-rc1.

Fixed status
mainline: [3b0daecfeac0103aba8b293df07a0cbaf8b43f29]
stable/4.19: [e6721ea845fcb93a764a92bd40f1afc0d6c69751]
stable/5.10: [fcbd99b3c73309107e3be71f20dff9414df64f91]
stable/5.15: [cbac7de1d9901521e78cdc34e15451df3611f2ad]
stable/5.4: [8b0564704255c6b3c6a7188e86939f754e1577c0]
stable/6.1: [e6768c6737f4c02cba193a3339f0cc2907f0b86a]
stable/6.6: [315eb3c2df7e4cb18e3eacfa18a53a46f2bf0ef7]

CVE-2023-52642: media: rc: bpf attach/detach requires write permission

Announce: https://lore.kernel.org/linux-cve-announce/2024041758-CVE-2023-52642-3261@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc5.
Affected functions were introduced by commit f4364dcf ("media: rc:
introduce BPF_PROG_LIRC_MODE2") in 4.18-rc1.

Fixed status
mainline: [6a9d552483d50953320b9d3b57abdee8d436f23f]
stable/5.10: [93d8109bf182510629bbefc8cd45296d2393987f]
stable/5.15: [d98210108e7b2ff64b332b0a3541c8ad6a0617b0]
stable/6.1: [9f6087851ec6dce5b15f694aeaf3e8ec8243224e]
stable/6.6: [93136132d1b5792bf44151e3494ae3691cd738e8]

CVE-2023-52643: iio: core: fix memleak in iio_device_register_sysfs

Announce: https://lore.kernel.org/linux-cve-announce/2024041701-CVE-2023-52643-8834@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 32f1717 ("iio: core: rework iio device group
creation") in v5.13-rc1.
Fixed in v6.8-rc5.

Fixed status
mainline: [95a0d596bbd0552a78e13ced43f2be1038883c81]
stable/5.15: [1c6d19c8cbf6abcea2c8fca2db26abca2cbf0363]
stable/6.1: [359f220d0e753bba840eac19ffedcdc816b532f2]
stable/6.6: [b90126c86d83912688501826643ea698f0df1728]

CVE-2023-52644: wifi: b43: Stop/wake correct queue in DMA Tx path when
QoS is disabled

Announce: https://lore.kernel.org/linux-cve-announce/2024041732-CVE-2023-52644-e2a7@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit e6f5b93 ("b43: Add QOS support") in v2.6.26-rc1.
Fixed in v6.9-rc1.

Fixed status
cip/4.4: [c96084a13a9184651de06b6a8b4c939838271e3d]
cip/4.4-st: [c96084a13a9184651de06b6a8b4c939838271e3d]
mainline: [9636951e4468f02c72cc75a82dc65d003077edbc]
stable/4.19: [1824f942527f784a19e01eac2d9679a21623d010]
stable/5.10: [49f067726ab01c87cf57566797a8a719badbbf08]
stable/5.15: [04a2b6eff2ae1c19cb7f41e803bcbfaf94c06455]
stable/5.4: [31aaf17200c336fe258b70d39c40645ae19d0240]
stable/6.1: [c67698325c68f8768db858f5c87c34823421746d]
stable/6.6: [bc845e2e42cae95172c04bf29807c480f51a2a83]

CVE-2023-52645: pmdomain: mediatek: fix race conditions with genpd

Announce: https://lore.kernel.org/linux-cve-announce/2024041733-CVE-2023-52645-68dc@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 59b644b ("soc: mediatek: Add MediaTek SCPSYS
power domains") in v5.11-rc1.
Fixed in v6.8-rc4.

Fixed status
mainline: [c41336f4d69057cbf88fed47951379b384540df5]
stable/5.15: [475426ad1ae0bfdfd8f160ed9750903799392438]
stable/6.1: [339ddc983bc1622341d95f244c361cda3da3a4ff]
stable/6.6: [f83b9abee9faa4868a6fac4669b86f4c215dae25]

CVE-2024-26818: tools/rtla: Fix clang warning about mount_point var size

Announce: https://lore.kernel.org/linux-cve-announce/2024041701-CVE-2024-26818-d65b@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit a957cbc ("rtla: Add -C cgroup support") in v6.5-rc1.
Fixed in v6.8-rc5.

Fixed status
mainline: [30369084ac6e27479a347899e74f523e6ca29b89]
stable/6.6: [8a585914c266dc044f53b5c83c170f79b45fcf9a]

CVE-2024-26819: dm: limit the number of targets and parameter size area

Announce: https://lore.kernel.org/linux-cve-announce/2024041701-CVE-2024-26819-1731@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc3.
It seems as if all stable kernels are affected.

Fixed status
mainline: [bd504bcfec41a503b32054da5472904b404341a4]
stable/5.10: [a891a0621e725e85529985139cada8cb5a74a116]
stable/5.15: [888a0a46b80fa37eacfe81faf47ba0b83876251d]
stable/6.1: [c5d83ac2bf6ca668a39ffb1a576899a66153ba19]
stable/6.6: [438d19492b7f002334573bae43276297eb234c80]

CVE-2024-26820: hv_netvsc: Register VF in netvsc_probe if
NET_DEVICE_REGISTER missed

Announce: https://lore.kernel.org/linux-cve-announce/2024041701-CVE-2024-26820-fc5a@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 8552085 ("hv_netvsc: Fix race of
register_netdevice_notifier and VF register") in v6.7-rc3.
This commit was backported to 4.19, 5.10, 5.15, 5.4, 6.1, and 6.6.
Linux 4.4 is not affected.
Fixed in v6.8-rc4.

Fixed status
mainline: [9cae43da9867412f8bd09aee5c8a8dc5e8dc3dc2]
stable/4.19: [bcb7164258d0a9a8aa2e73ddccc2d78f67d2519d]
stable/5.10: [5b10a88f64c0315cfdef45de0aaaa4eef57de0b7]
stable/5.15: [b6d46f306b3964d05055ddaa96b58cd8bd3a472c]
stable/5.4: [c7441c77c91e47f653104be8353b44a3366a5366]
stable/6.1: [309ef7de5d840e17607e7d65cbf297c0564433ef]
stable/6.6: [a71302c8638939c45e4ba5a99ea438185fd3f418]

CVE-2024-26821: fs: relax mount_setattr() permission checks

Announce: https://lore.kernel.org/linux-cve-announce/2024041702-CVE-2024-26821-de6b@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc5.
Affected function was introduced by commit 2a18672 ("fs: add
mount_setattr()") in v5.12-rc1-dontuse.
So, 4.4, 4.19, 5.4, and 5.10 are not affected.

Fixed status
mainline: [46f5ab762d048dad224436978315cbc2fa79c630]
stable/6.1: [95de4ad173ca0e61034f3145d66917970961c210]
stable/6.6: [31f71f2d7a081fc6c6bdf06865beedf6db5b0ca4]

CVE-2024-26822: smb: client: set correct id, uid and cruid for
multiuser automounts

Announce: https://lore.kernel.org/linux-cve-announce/2024041702-CVE-2024-26822-04b5@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 9fd29a5 ("cifs: use fs_context for automounts")
in v6.2-rc1.
Fixed in v6.8-rc5.

Fixed status
mainline: [4508ec17357094e2075f334948393ddedbb75157]
stable/6.6: [c2aa2718cda2d56b4a551cb40043e9abc9684626]

CVE-2024-26823: irqchip/gic-v3-its: Restore quirk probing for ACPI-based systems

Announce: https://lore.kernel.org/linux-cve-announce/2024041702-CVE-2024-26823-0e52@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 9585a49 ("irqchip/gic-v3-its: Split allocation
from initialisation of its_node") in v6.6-rc6.
This commit was backported to 6.1 and 5.15.
Fixed in v6.8-rc5.

Fixed status
mainline: [8b02da04ad978827e5ccd675acf170198f747a7a]
stable/6.6: [91a80fff3eeed928b6fba21271f6a9719b22a5d8]

CVE-2024-26824: crypto: algif_hash - Remove bogus SGL free on
zero-length error path

Announce: https://lore.kernel.org/linux-cve-announce/2024041702-CVE-2024-26824-98e1@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit b6d972f ("crypto: af_alg/hash: Fix recvmsg()
after sendmsg(MSG_MORE)") in v6.5-rc1.
Fixed in v6.8-rc4.

Fixed status
mainline: [24c890dd712f6345e382256cae8c97abb0406b70]
stable/6.6: [9c82920359b7c1eddaf72069bcfe0ffddf088cd0]

CVE-2024-26825: nfc: nci: free rx_data_reassembly skb on NCI device cleanup

Announce: https://lore.kernel.org/linux-cve-announce/2024041702-CVE-2024-26825-408e@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 6a2968a ("NFC: basic NCI protocol
implementation") in v3.2-rc1.
Fixed in v6.8-rc3.

Fixed status
cip/4.4: [8cfb41cc7ae740f0ab1721db1298c2bb1a0f9b56]
cip/4.4-rt: [8cfb41cc7ae740f0ab1721db1298c2bb1a0f9b56]
cip/4.4-st: [8cfb41cc7ae740f0ab1721db1298c2bb1a0f9b56]
mainline: [bfb007aebe6bff451f7f3a4be19f4f286d0d5d9c]
stable/4.19: [7e9a8498658b398bf11b8e388005fa54e40aed81]
stable/5.10: [2f6d16f0520d6505241629ee2f5c131b547d5f9d]
stable/5.15: [471c9ede8061357b43a116fa692e70d91941ac23]
stable/5.4: [71349abe3aba7fedcab5b3fcd7aa82371fb5ccbf]
stable/6.1: [5c0c5ffaed73cbae6c317374dc32ba6cacc60895]
stable/6.6: [16d3f507b0fa70453dc54550df093d6e9ac630c1]

CVE-2024-26826: mptcp: fix data re-injection from stale subflow

Announce: https://lore.kernel.org/linux-cve-announce/2024041703-CVE-2024-26826-b984@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 1e1d9d6 ("mptcp: handle pending data on closed
subflow") in v5.15-rc1.
Fixed in v6.8-rc3.

Fixed status
mainline: [b6c620dc43ccb4e802894e54b651cf81495e9598]
stable/5.15: [6f95120f898b40d13fd441225ef511307853c9c2]
stable/6.1: [6673d9f1c2cd984390550dbdf7d5ae07b20abbf8]
stable/6.6: [b609c783c535493aa3fca22c7e40a120370b1ca5]

CVE-2024-26827: i2c: qcom-geni: Correct I2C TRE sequence

Announce: https://lore.kernel.org/linux-cve-announce/2024041703-CVE-2024-26827-67c1@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit d870355 ("i2c: qcom-geni: Add support for GPI
DMA") in v5.18-rc1.
Fixed in v6.8-rc5.

Fixed status
mainline: [83ef106fa732aea8558253641cd98e8a895604d7]
stable/6.1: [083870b029c06da6a9a49340dd78637eec35a1d4]
stable/6.6: [0589dff4fbf4a7b88a909a34ecfa7b5d3daf51f5]

CVE-2024-26828: cifs: fix underflow in parse_server_interfaces()

Announce: https://lore.kernel.org/linux-cve-announce/2024041703-CVE-2024-26828-b2be@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit fe856be ("CIFS: parse and store info on iface
queries") in v4.18-rc2.
Fixed in v6.8-rc5.

Fixed status
mainline: [cffe487026be13eaf37ea28b783d9638ab147204]
stable/6.1: [7190353835b4a219abb70f90b06cdcae97f11512]
stable/6.6: [f7ff1c89fb6e9610d2b01c1821727729e6609308]

CVE-2024-26829: media: ir_toy: fix a memleak in irtoy_tx

Announce: https://lore.kernel.org/linux-cve-announce/2024041716-CVE-2024-26829-e879@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 4114978 ("media: ir_toy: prevent device from
hanging during transmit") in v5.16-rc1.
This commit was backported to 5.15.
Fixed in v6.8-rc5.

Fixed status
mainline: [dc9ceb90c4b42c6e5c6757df1d6257110433788e]
stable/5.10: [486a4176bc783df798bce2903824801af8d2c3ae]
stable/5.15: [207557e393a135c1b6fe1df7cc0741d2c1789fff]
stable/6.1: [be76ad74a43f90f340f9f479e6b04f02125f6aef]
stable/6.6: [7219a692ffc00089015ada33b85b334d1a4b6e8e]

CVE-2024-26830: i40e: Do not allow untrusted VF to remove
administratively set MAC

Announce: https://lore.kernel.org/linux-cve-announce/2024041703-CVE-2024-26830-5bc0@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 700bbf6 ("i40e: allow VF to remove any MAC
filter") in v3.14-rc1.
Introduced by commit ceb2947 ("i40e: Add support for VF to specify its
primary MAC address") in v6.4-rc1.
Fixed in v6.8-rc5.

Fixed status
mainline: [73d9629e1c8c1982f13688c4d1019c3994647ccc]
stable/6.1: [1c981792e4ccbc134b468797acdd7781959e6893]
stable/6.6: [be147926140ac48022c9605d7ab0a67387e4b404]

CVE-2024-26831: net/handshake: Fix handshake_req_destroy_test1

Announce: https://lore.kernel.org/linux-cve-announce/2024041704-CVE-2024-26831-2e6e@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 4a0f07d ("net/handshake: Fix memory leak in
__sock_create() and sock_alloc_file()") in v6.6-rc3.
Fixed in v6.8-rc5.

Fixed status
mainline: [4e1d71cabb19ec2586827adfc60d68689c68c194]
stable/6.6: [d74226e03df1bf19848f18344401f254345af912]

CVE-2024-26832: mm: zswap: fix missing folio cleanup in writeback race path

Announce: https://lore.kernel.org/linux-cve-announce/2024041714-CVE-2024-26832-77ce@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 04fc781 ("mm: fix zswap writeback race
condition") in v6.4-rc3.
This commit was backported to 6.1.
Fixed in v6.8-rc6.

Fixed status
mainline: [e3b63e966cac0bf78aaa1efede1827a252815a1d]
stable/6.1: [14f1992430ef9e647b02aa8ca12c5bcb9a1dffea]
stable/6.6: [6156277d1b26cb3fdb6fcbf0686ab78268571644]

CVE-2024-26833: drm/amd/display: Fix memory leak in dm_sw_fini()

Announce: https://lore.kernel.org/linux-cve-announce/2024041714-CVE-2024-26833-b435@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 743b978 ("drm/amd/display: Hook up the DMUB
service in DM") in v5.6-rc1.
Fixed in v6.8-rc6.

Fixed status
mainline: [bae67893578d608e35691dcdfa90c4957debf1d3]
stable/5.10: [b49b022f7dfce85eb77d0d987008fde5c01d7857]
stable/5.15: [33f649f1b1cea39ed360e6c12bba4fac83118e6e]
stable/6.1: [58168005337eabef345a872be3f87d0215ff3b30]
stable/6.6: [10c6b90e975358c17856a578419dc449887899c2]

CVE-2024-26834: netfilter: nft_flow_offload: release dst in case
direct xmit path is used

Announce: https://lore.kernel.org/linux-cve-announce/2024041714-CVE-2024-26834-a73b@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit fa502c8 ("netfilter: flowtable: simplify route
logic") in v6.5-rc1.
This commit was backported to 5.15 and 6.1.
Fixed in v6.6.19.

Fixed status
mainline: [8762785f459be1cfe6fcf7285c123aad6a3703f0]
stable/5.15: [13b57b5cd591d5b22f9bbf047b2922967de411f3]
stable/6.1: [a6cafdb49a7bbf4a88367db209703eee6941e023]
stable/6.6: [9256ab9232e35a16af9c30fa4e522e6d1bd3605a]

CVE-2024-26835: netfilter: nf_tables: set dormant flag on hook register failure

Announce: https://lore.kernel.org/linux-cve-announce/2024041714-CVE-2024-26835-083d@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 179d9ba ("netfilter: nf_tables: fix table flag
updates") in v5.13-rc5.
This commit was backported to 5.4 and 5.10.
Fixed in v6.8-rc6.

Fixed status
mainline: [bccebf64701735533c8db37773eeacc6566cc8ec]
stable/5.10: [31ea574aeca1aa488e18716459bde057217637af]
stable/5.15: [664264a5c55bf97a9c571c557d477b75416199be]
stable/5.4: [ae4360cbd385f0d7a8a86d5723e50448cc6318f3]
stable/6.1: [0c9302a6da262e6ab6a6c1d30f04a6130ed97376]
stable/6.6: [f2135bbf14949687e96cabb13d8a91ae3deb9069]

CVE-2024-26836: platform/x86: think-lmi: Fix password opcode ordering
for workstations

Announce: https://lore.kernel.org/linux-cve-announce/2024041714-CVE-2024-26836-19c3@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 640a5fa ("platform/x86: think-lmi: Opcode
support") in v5.17-rc1.
Fixed in v6.8-rc6.

Fixed status
mainline: [6f7d0f5fd8e440c3446560100ac4ff9a55eec340]

CVE-2024-26837: net: bridge: switchdev: Skip MDB replays of deferred
events on offload

Announce: https://lore.kernel.org/linux-cve-announce/2024041715-CVE-2024-26837-753c@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 4f2673b ("net: bridge: add helper to replay port
and host-joined mdb entries") in v5.13-rc1.
Fixed in v6.8-rc6.

Fixed status
mainline: [dc489f86257cab5056e747344f17a164f63bff4b]
stable/6.1: [2d5b4b3376fa146a23917b8577064906d643925f]
stable/6.6: [603be95437e7fd85ba694e75918067fb9e7754db]

CVE-2024-26838: RDMA/irdma: Fix KASAN issue with tasklet

Announce: https://lore.kernel.org/linux-cve-announce/2024041715-CVE-2024-26838-2fdb@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 44d9e52 ("RDMA/irdma: Implement device
initialization definitions") in v5.14-rc1.
Fixed in v6.8-rc6.

Fixed status
mainline: [bd97cea7b18a0a553773af806dfbfac27a7c4acb]
stable/5.15: [635d79aa477f9912e602feb5498bdd51fb9cb824]
stable/6.1: [b2e4a5266e3d133b4c7f0e43bf40d13ce14fd1aa]
stable/6.6: [c6f1ca235f68b22b3e691b2ea87ac285e5946848]

CVE-2024-26839: IB/hfi1: Fix a memleak in init_credit_return

Announce: https://lore.kernel.org/linux-cve-announce/2024041715-CVE-2024-26839-1196@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 7724105 ("IB/hfi1: add driver files") in v4.3-rc1.
Fixed in v6.8-rc6.

Fixed status
cip/4.4: [9528ec86a46ddbbfe876277bd169decc45686446]
cip/4.4-st: [9528ec86a46ddbbfe876277bd169decc45686446]
mainline: [809aa64ebff51eb170ee31a95f83b2d21efa32e2]
stable/4.19: [2e4f9f20b32658ef3724aa46f7aef4908d2609e3]
stable/5.10: [3fa240bb6b2dbb3e7a3ee1440a4889cbb6207eb7]
stable/5.15: [52de5805c147137205662af89ed7e083d656ae25]
stable/5.4: [cecfb90cf71d91e9efebd68b9e9b84661b277cc8]
stable/6.1: [f0d857ce31a6bc7a82afcdbadb8f7417d482604b]
stable/6.6: [b41d0ade0398007fb746213f09903d52a920e896]

CVE-2024-26840: cachefiles: fix memory leak in cachefiles_add_cache()

Announce: https://lore.kernel.org/linux-cve-announce/2024041715-CVE-2024-26840-057d@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 9ae326a ("CacheFiles: A cache that backs onto a
mounted filesystem") in v2.6.30-rc1.
Fixed in v6.8-rc6.

Fixed status
cip/4.4: [aef24c9d27c5c28ca43e240a338698183b8e0ee0]
cip/4.4-st: [aef24c9d27c5c28ca43e240a338698183b8e0ee0]
mainline: [e21a2f17566cbd64926fb8f16323972f7a064444]
stable/4.19: [cb5466783793e66272624cf71925ae1d1ba32083]
stable/5.10: [43eccc5823732ba6daab2511ed32dfc545a666d8]
stable/5.15: [94965be37add0983672e48ecb33cdbda92b62579]
stable/5.4: [037d5a949b0455540ef9aab34c10ddf54b65d285]
stable/6.1: [8b218e2f0a27a9f09428b1847b4580640b9d1e58]
stable/6.6: [38e921616320d159336b0ffadb09e9fb4945c7c3]

CVE-2024-26841: LoongArch: Update cpu_sibling_map when disabling nonboot CPUs

Announce: https://lore.kernel.org/linux-cve-announce/2024041716-CVE-2024-26841-6433@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc6.

Fixed status
mainline: [752cd08da320a667a833803a8fd6bb266114cce5]
stable/6.6: [b1ec3d6b86fdd057559a5908e6668279bf770e0e]

CVE-2024-26842: scsi: ufs: core: Fix shift issue in ufshcd_clear_cmd()

Announce: https://lore.kernel.org/linux-cve-announce/2024041716-CVE-2024-26842-d556@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc4.
The shift operation was introduced by commit 7aa12d2f ("scsi: ufs:
core: Update the ufshcd_clear_cmds() functionality") in 6.5-rc1.

Fixed status
mainline: [b513d30d59bb383a6a5d6b533afcab2cee99a8f8]
stable/6.6: [7ac9e18f5d66087cd22751c5c5bf0090eb0038fe]

CVE-2024-26843: efi: runtime: Fix potential overflow of soft-reserved
region size

Announce: https://lore.kernel.org/linux-cve-announce/2024041716-CVE-2024-26843-51a0@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc4.
Vulnerability in the drivers/firmware/efi/arm-runtime.c was introduced
by commit 16993c0 ("arm/efi: EFI soft reservation to memblock") in
5.5-rc1.
Vulnerability in the  drivers/firmware/efi/riscv-runtime.c  was
introduced by commit de1034b3 ("efi: runtime: Fix potential overflow
of soft-reserved region size") in 6.8-rc4.

Fixed status
mainline: [de1034b38a346ef6be25fe8792f5d1e0684d5ff4]
stable/5.10: [4fff3d735baea104017f2e3c245e27cdc79f2426]
stable/5.15: [4aa36b62c3eaa869860bf78b1146e9f2b5f782a9]
stable/6.1: [700c3f642c32721f246e09d3a9511acf40ae42be]
stable/6.6: [cf3d6813601fe496de7f023435e31bfffa74ae70]

CVE-2024-26844: block: Fix WARNING in _copy_from_iter

Announce: https://lore.kernel.org/linux-cve-announce/2024041716-CVE-2024-26844-c534@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc2.
It looks as if all stable kernels are affected.
For instance, 4.4.302 does the following check. That may need to split
conditional check when map_data->from_user is set.

    if (((iter->type & WRITE) && (!map_data || !map_data->null_mapped)) ||
        (map_data && map_data->from_user)) {
        ret = bio_copy_from_iter(bio, *iter);

Fixed status
mainline: [13f3956eb5681a4045a8dfdef48df5dc4d9f58a6]
stable/6.1: [8fc80874103a5c20aebdc2401361aa01c817f75b]
stable/6.6: [0f1bae071de9967602807472921829a54b2e5956]

CVE-2024-26845: scsi: target: core: Add TMF to tmr_list handling

Announce: https://lore.kernel.org/linux-cve-announce/2024041717-CVE-2024-26845-90d2@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc1.

Fixed status
cip/4.4: [81c6ef786db65985883e0066b687247386fc8d36]
cip/4.4-rt: [81c6ef786db65985883e0066b687247386fc8d36]
cip/4.4-st: [81c6ef786db65985883e0066b687247386fc8d36]
mainline: [83ab68168a3d990d5ff39ab030ad5754cbbccb25]
stable/4.19: [425a571a7e6fc389954cf2564e1edbba3740e171]
stable/5.10: [168ed59170de1fd7274080fe102216162d6826cf]
stable/5.15: [a9849b67b4402a12eb35eadc9306c1ef9847d53d]
stable/5.4: [11f3fe5001ed05721e641f0ecaa7a73b7deb245d]
stable/6.1: [e717bd412001495f17400bfc09f606f1b594ef5a]
stable/6.6: [36bc5040c863b44af06094b22f1e50059227b9cb]

CVE-2024-26846: nvme-fc: do not wait in vain when unloading module

Announce: https://lore.kernel.org/linux-cve-announce/2024041717-CVE-2024-26846-9593@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc3.
The drivers/nvme/host/fc.c was introduced by commit e399441
("nvme-fabrics: Add host support for FC transport") in 4.10-rc1.
Then added wait_for_completion and such by commit 4c73cbd ("nvme-fc:
fix module unloads while lports still pending") in 5.3-rc1.

Fixed status
mainline: [70fbfc47a392b98e5f8dba70c6efc6839205c982]
stable/5.10: [4f2c95015ec2a1899161be6c0bdaecedd5a7bfb2]
stable/5.15: [0bf567d6d9ffe09e059bbdfb4d07143cef42c75c]
stable/6.1: [085195aa90a924c79e35569bcdad860d764a8e17]
stable/6.6: [baa6b7eb8c66486bd64608adc63fe03b30d3c0b9]

CVE-2024-26847: powerpc/rtas: use correct function name for resetting TCE tables

Announce: https://lore.kernel.org/linux-cve-announce/2024041753-CVE-2024-26847-953f@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 8252b88 ("powerpc/rtas: improve function
information lookups") in v6.3-rc1.
Fixed in v6.8-rc7.

Fixed status
mainline: [fad87dbd48156ab940538f052f1820f4b6ed2819]
stable/6.6: [6b6282d56b14879124416a23837af9bd52ae2dfb]

CVE-2024-26848: afs: Fix endless loop in directory parsing

Announce: https://lore.kernel.org/linux-cve-announce/2024041753-CVE-2024-26848-0413@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 57e9d49c ("afs: Hide silly-rename files from
userspace") in 6.8-rc2.
This commit was backported to 5.10, 5.15, 5.4, 6.1, and 6.6.
Fixed in 6.8-rc7.

Fixed status
mainline: [5f7a07646655fb4108da527565dcdc80124b14c4]
stable/5.10: [b94f434fe977689da4291dc21717790b9bd1c064]
stable/5.15: [a6ffae61ad9ebf2fdcb943135b2f30c85f49cd27]
stable/5.4: [854ebf45a4ddd4cadeffb6644e88d19020634e1a]
stable/6.1: [76426abf9b980b46983f97de8e5b25047b4c9863]
stable/6.6: [106e14ca55a0acb3236ee98813a1d243f8aa2d05]

CVE-2024-26849: netlink: add nla be16/32 types to minlen array

Announce: https://lore.kernel.org/linux-cve-announce/2024041754-CVE-2024-26849-9e3c@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit ecaf75f ("netlink: introduce bigendian integer
types") in v6.1-rc4.
Fixed in v6.8-rc7.

Fixed status
mainline: [9a0d18853c280f6a0ee99f91619f2442a17a323a]
stable/6.1: [0ac219c4c3ab253f3981f346903458d20bacab32]
stable/6.6: [a2ab028151841cd833cb53eb99427e0cc990112d]

CVE-2024-26850: mm/debug_vm_pgtable: fix BUG_ON with pud advanced test

Announce: https://lore.kernel.org/linux-cve-announce/2024041754-CVE-2024-26850-f608@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 27af67f ("powerpc/book3s64/mm: enable transparent
pud hugepage") in v6.6-rc1.
Fixed in v6.8-rc7.

Fixed status
mainline: [720da1e593b85a550593b415bf1d79a053133451]
stable/6.6: [d2a9510c0e39d06f5544075c13040407bdbf2803]

CVE-2024-26851: netfilter: nf_conntrack_h323: Add protection for bmp
length out of range

Announce: https://lore.kernel.org/linux-cve-announce/2024041723-CVE-2024-26851-4652@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 5e35941 ("[NETFILTER]: Add H.323 conntrack/NAT
helper") in v2.6.20.16.
Fixed in v6.8.

Fixed status
cip/4.4: [b135d56fd7ad317bb15239c58c28bcf2590fd4d2]
cip/4.4-st: [b135d56fd7ad317bb15239c58c28bcf2590fd4d2]
mainline: [767146637efc528b5e3d31297df115e85a2fd362]
stable/4.19: [98db42191329c679f4ca52bec0b319689e1ad8cb]
stable/5.10: [ccd1108b16ab572d9bf635586b0925635dbd6bbc]
stable/5.15: [b3c0f553820516ad4b62a9390ecd28d6f73a7b13]
stable/5.4: [4bafcc43baf7bcf93566394dbd15726b5b456b7a]
stable/6.1: [39001e3c42000e7c2038717af0d33c32319ad591]
stable/6.6: [014a807f1cc9c9d5173c1cd935835553b00d211c]

CVE-2024-26852: net/ipv6: avoid possible UAF in ip6_route_mpath_notify()

Announce: https://lore.kernel.org/linux-cve-announce/2024041723-CVE-2024-26852-0057@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 3b1137f ("net: ipv6: Change notifications for
multipath add to RTA_MULTIPATH") in v4.11-rc1.
Fixed in v6.8.

Fixed status
mainline: [685f7d531264599b3f167f1e94bbd22f120e5fab]
stable/4.19: [31ea5bcc7d4cd1423de6be327a2c034725704136]
stable/5.10: [79ce2e54cc0ae366f45516c00bf1b19aa43e9abe]
stable/5.15: [cae3303257950d03ffec2df4a45e836f10d26c24]
stable/5.4: [664f9c647260cc9d68b4e31d9899530d89dd045e]
stable/6.1: [394334fe2ae3b9f1e2332b873857e84cb28aac18]
stable/6.6: [ed883060c38721ed828061f6c0c30e5147326c9a]

CVE-2024-26853: igc: avoid returning frame twice in XDP_REDIRECT

Announce: https://lore.kernel.org/linux-cve-announce/2024041723-CVE-2024-26853-b549@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 4ff3203 ("igc: Add support for XDP_REDIRECT
action") in v5.13-rc1.
Fixed in v6.8.

Fixed status
mainline: [ef27f655b438bed4c83680e4f01e1cde2739854b]
stable/6.1: [63a3c1f3c9ecc654d851e7906d05334cd0c236e2]
stable/6.6: [8df393af9e7e8dfd62e9c41dbaa4d2ff53bf794a]

CVE-2024-26854: ice: fix uninitialized dplls mutex usage

Announce: https://lore.kernel.org/linux-cve-announce/2024041724-CVE-2024-26854-1a41@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit d7999f5 ("ice: implement dpll interface to
control cgu") in v6.7-rc1.
Fixed in v6.8.

Fixed status
mainline: [9224fc86f1776193650a33a275cac628952f80a9]

CVE-2024-26855: net: ice: Fix potential NULL pointer dereference in
ice_bridge_setlink()

Announce: https://lore.kernel.org/linux-cve-announce/2024041724-CVE-2024-26855-ac0d@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit b1edc14 ("ice: Implement ice_bridge_getlink and
ice_bridge_setlink") in v4.20-rc1.
Fixed in v6.8.

Fixed status
mainline: [06e456a05d669ca30b224b8ed962421770c1496c]
stable/5.10: [37fe99016b12d32100ce670216816dba6c48b309]
stable/5.15: [8d95465d9a424200485792858c5b3be54658ce19]
stable/5.4: [d9fefc51133107e59d192d773be86c1150cfeebb]
stable/6.1: [afdd29726a6de4ba27cd15590661424c888dc596]
stable/6.6: [1a770927dc1d642b22417c3e668c871689fc58b3]

CVE-2024-26856: net: sparx5: Fix use after free inside sparx5_del_mact_entry

Announce: https://lore.kernel.org/linux-cve-announce/2024041724-CVE-2024-26856-3dbf@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit b37a1ba ("net: sparx5: add mactable support") in v5.14-rc1.
Fixed in v6.8.

Fixed status
mainline: [89d72d4125e94aa3c2140fedd97ce07ba9e37674]
stable/5.15: [e46274df1100fb0c06704195bfff5bfbd418bf64]
stable/6.1: [0de693d68b0a18d5e256556c7c62d92cca35ad52]
stable/6.6: [e83bebb718fd1f42549358730e1206164e0861d6]

CVE-2024-26857: geneve: make sure to pull inner header in geneve_rx()

Announce: https://lore.kernel.org/linux-cve-announce/2024041724-CVE-2024-26857-75ac@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 2d07dc7 ("geneve: add initial netdev driver for
GENEVE tunnels") in v4.2-rc1.
Fixed in v6.8.

Fixed status
mainline: [1ca1ba465e55b9460e4e75dec9fff31e708fec74]
stable/4.19: [e431c3227864b5646601c97f5f898d99472f2914]
stable/5.10: [c7137900691f5692fe3de54566ea7b30bb35d66c]
stable/5.15: [e77e0b0f2a11735c64b105edaee54d6344faca8a]
stable/5.4: [59d2a4076983303f324557a114cfd5c32e1f6b29]
stable/6.1: [c0b22568a9d8384fd000cc49acb8f74bde40d1b5]
stable/6.6: [0ece581d2a66e8e488c0d3b3e7b5760dbbfdbdd5]

CVE-2024-26858: net/mlx5e: Use a memory barrier to enforce PTP WQ xmit
submission tracking occurs after populating the metadata_map

Announce: https://lore.kernel.org/linux-cve-announce/2024041725-CVE-2024-26858-34fb@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 7e3f3ba ("net/mlx5e: Track xmit submission to PTP
WQ after populating metadata map") in v6.7-rc2.
Fixed in v6.8.

Fixed status
mainline: [b7cf07586c40f926063d4d09f7de28ff82f62b2a]
stable/6.6: [d1f71615dbb305f14f3b756cce015d70d8667549]

CVE-2024-26859: net/bnx2x: Prevent access to a freed page in page_pool

Announce: https://lore.kernel.org/linux-cve-announce/2024041735-CVE-2024-26859-a906@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 4cace67 ("bnx2x: Alloc 4k fragment for each rx
ring buffer element") in v4.2-rc1.
Fixed in v6.9-rc1.

Fixed status
cip/4.4: [34e08399bc377c023a40ab0811d61c86bda69871]
cip/4.4-st: [34e08399bc377c023a40ab0811d61c86bda69871]
mainline: [d27e2da94a42655861ca4baea30c8cd65546f25d]
stable/4.19: [7bcc090c81116c66936a7415f2c6b1483a4bcfd9]
stable/5.10: [8eebff95ce9558be66a36aa7cfb43223f3ab4699]
stable/5.15: [8ffcd3ccdbda0c918c4a0f922ef1c17010f1b598]
stable/5.4: [4f37d3a7e004bbf560c21441ca9c022168017ec4]
stable/6.1: [cf7d8cba639ae792a42c2a137b495eac262ac36c]
stable/6.6: [3a9f78b297e08ca8e88ae3ecff1f6fe2766dc5eb]

CVE-2024-26860: dm-integrity: fix a memory leak when rechecking the data

Announce: https://lore.kernel.org/linux-cve-announce/2024041735-CVE-2024-26860-ebf5@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit c88f5e5 ("dm-integrity: recheck the integrity tag
after a failure") in v6.8-rc6.
This commit was backported to 6.1 and 6.6.
Fixed in v6.9-rc1.

Fixed status
mainline: [55e565c42dce81a4e49c13262d5bc4eb4c2e588a]
stable/6.1: [20e21c3c0195d915f33bc7321ee6b362177bf5bf]
stable/6.6: [338580a7fb9b0930bb38098007e89cc0fc496bf7]

CVE-2024-26861: wireguard: receive: annotate data-race around
receiving_counter.counter

Announce: https://lore.kernel.org/linux-cve-announce/2024041736-CVE-2024-26861-3a78@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit a9e90d9 ("wireguard: noise: separate receive
counter from send counter") in v5.7-rc7.
Fixed in v6.9-rc1.

Fixed status
mainline: [bba045dc4d996d03dce6fe45726e78a1a1f6d4c3]
stable/5.10: [f87884e0dffd61b47e58bc6e1e2f6843c212b0cc]
stable/5.15: [d691be84ab898cf136a35176eaf2f8fc116563f0]
stable/6.1: [45a83b220c83e3c326513269afbf69ae6fc65cce]
stable/6.6: [78739d72f16b2d7d549f713f1dfebd678d32484b]

CVE-2024-26862: packet: annotate data-races around ignore_outgoing

Announce: https://lore.kernel.org/linux-cve-announce/2024041736-CVE-2024-26862-2605@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit fa788d9 ("packet: add sockopt to ignore outgoing
packets") in v4.20-rc1.
Fixed in v6.9-rc1.

Fixed status
mainline: [6ebfad33161afacb3e1e59ed1c2feefef70f9f97]
stable/5.10: [68e84120319d4fc298fcdb14cf0bea6a0f64ffbd]
stable/5.15: [d35b62c224e70797f8a1c37fe9bc4b3e294b7560]
stable/5.4: [84c510411e321caff3c07e6cd0f917f06633cfc0]
stable/6.1: [ef7eed7e11d23337310ecc2c014ecaeea52719c5]
stable/6.6: [2c02c5059c78a52d170bdee4a369b470de6deb37]

CVE-2024-26863: hsr: Fix uninit-value access in hsr_get_node()

Announce: https://lore.kernel.org/linux-cve-announce/2024041736-CVE-2024-26863-b742@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit f266a68 ("net/hsr: Better frame dispatch") in v3.17-rc1.
Fixed in v6.9-rc1.

Fixed status
mainline: [ddbec99f58571301679addbc022256970ca3eac6]
stable/4.19: [e3b2bfb8ff1810a537b2aa55ba906a6743ed120c]
stable/5.10: [7fb2d4d6bb1c85f7a23aace0ed6c86a95dea792a]
stable/5.15: [a809bbfd0e503351d3051317288a70a4569a4949]
stable/5.4: [889ed056eae7fda85b769a9ab33c093379c45428]
stable/6.1: [1ed222ca7396938eb1ab2d034f1ba0d8b00a7122]
stable/6.6: [39cc316fb3bc5e7c9dc5eed314fe510d119c6862]

CVE-2024-26864: tcp: Fix refcnt handling in __inet_hash_connect().

Announce: https://lore.kernel.org/linux-cve-announce/2024041736-CVE-2024-26864-397c@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 66b60b0 ("dccp/tcp: Unhash sk from ehash for tb2
alloc failure after check_estalblished().") in v6.8-rc6.
This commit was backported to 6.1 and 6.6.
Fixed in v6.9-rc1.

Fixed status
mainline: [04d9d1fc428ac9f581d55118d67e0cb546701feb]
stable/6.1: [86d9b040421bbd26425f5a3edc226f57ecdecbfe]
stable/6.6: [856baaa100cd288d3685eedae9a129c996e7e755]

CVE-2024-26865: rds: tcp: Fix use-after-free of net in reqsk_timer_handler().

Announce: https://lore.kernel.org/linux-cve-announce/2024041737-CVE-2024-26865-56dc@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 467fa15 ("RDS-TCP: Support multiple RDS-TCP
listen endpoints, one per netns.") in v4.3-rc1.
Fixed in v6.9-rc1.

Fixed status
mainline: [2a750d6a5b365265dbda33330a6188547ddb5c24]
stable/6.1: [9905a157048f441f1412e7bd13372f4a971d75c6]
stable/6.6: [f901ee07853ce97e9f1104c7c898fbbe447f0279]

CVE-2024-26866: spi: lpspi: Avoid potential use-after-free in probe()

Announce: https://lore.kernel.org/linux-cve-announce/2024041737-CVE-2024-26866-1e98@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 5314987 ("spi: imx: add lpspi bus driver") in v4.10-rc1.
Fixed in v6.9-rc1.

Fixed status
mainline: [2ae0ab0143fcc06190713ed81a6486ed0ad3c861]
stable/6.6: [da83ed350e4604b976e94239b08d8e2e7eaee7ea]

CVE-2024-26867: comedi: comedi_8255: Correct error in subdevice initialization

Announce: https://lore.kernel.org/linux-cve-announce/2024041737-CVE-2024-26867-45ad@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 5c57b1c ("comedi: comedi_8255: Rework subdevice
initialization functions") in v6.7-rc1.
Fixed in v6.8.

Fixed status
mainline: [cfa9ba1ae0bef0681833a22d326174fe633caab5]
stable/6.8: [cfa9ba1ae0bef0681833a22d326174fe633caab5]

CVE-2024-26868: nfs: fix panic when nfs4_ff_layout_prepare_ds() fails

Announce: https://lore.kernel.org/linux-cve-announce/2024041737-CVE-2024-26868-35ff@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit b739a5b ("NFSv4/flexfiles: Cancel I/O if the
layout is recalled or revoked") in v6.1-rc1.
Fixed in v6.9-rc1.

Fixed status
mainline: [719fcafe07c12646691bd62d7f8d94d657fa0766]
stable/6.1: [31db25e3141b20e2a76a9f219eeca52e3cab126c]
stable/6.6: [7ca651b4ec4a049f5a46a0e5ff921b86b91c47c5]

CVE-2024-26869: f2fs: fix to truncate meta inode pages forcely

Announce: https://lore.kernel.org/linux-cve-announce/2024041738-CVE-2024-26869-c9e2@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 6aa58d8 ("f2fs: readahead encrypted block during
GC") in v4.19-rc1.
Introduced by commit e3b49ea ("f2fs: invalidate META_MAPPING before
IPU/DIO write") in v5.16-rc1.
Commit e3b49ea was backported to 5.15.
Fixed in v6.9-rc1.

Fixed status
mainline: [9f0c4a46be1fe9b97dbe66d49204c1371e3ece65]
stable/6.6: [c92f2927df860a60ba815d3ee610a944b92a8694]

CVE-2024-26870: NFSv4.2: fix nfs4_listxattr kernel BUG at mm/usercopy.c:102

Announce: https://lore.kernel.org/linux-cve-announce/2024041738-CVE-2024-26870-7aea@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 012a211 ("NFSv4.2: hook in the user extended
attribute handlers") in v5.9-rc1.
Fixed in v6.9-rc1.

Fixed status
mainline: [251a658bbfceafb4d58c76b77682c8bf7bcfad65]
stable/5.10: [4403438eaca6e91f02d272211c4d6b045092396b]
stable/5.15: [9d52865ff28245fc2134da9f99baff603a24407a]
stable/6.1: [06e828b3f1b206de08ef520fc46a40b22e1869cb]
stable/6.6: [79cdcc765969d23f4e3d6ea115660c3333498768]

CVE-2024-26871: f2fs: fix NULL pointer dereference in f2fs_submit_page_write()

Announce: https://lore.kernel.org/linux-cve-announce/2024041738-CVE-2024-26871-670f@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit e067dc3 ("f2fs: maintain six open zones for zoned
devices") in v6.5-rc1.
Fixed in v6.9-rc1.

Fixed status
mainline: [c2034ef6192a65a986a45c2aa2ed05824fdc0e9f]
stable/6.6: [8e2ea8b04cb8d976110c4568509e67d6a39b2889]

CVE-2024-26872: RDMA/srpt: Do not register event handler until srpt
device is fully setup

Announce: https://lore.kernel.org/linux-cve-announce/2024041738-CVE-2024-26872-2d38@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit a42d985 ("ib_srpt: Initial SRP Target merge for
v3.3-rc1") in v3.3-rc1.
Fixed in v6.9-rc1.

Fixed status
mainline: [c21a8870c98611e8f892511825c9607f1e2cd456]
stable/5.10: [bdd895e0190c464f54f84579e7535d80276f0fc5]
stable/5.15: [6413e78086caf7bf15639923740da0d91fdfd090]
stable/6.1: [e362d007294955a4fb929e1c8978154a64efdcb6]
stable/6.6: [85570b91e4820a0db9d9432098778cafafa7d217]
stable/6.8: [ec77fa12da41260c6bf9e060b89234b980c5130f]

CVE-2024-26873: scsi: hisi_sas: Fix a deadlock issue related to automatic dump

Announce: https://lore.kernel.org/linux-cve-announce/2024041739-CVE-2024-26873-e310@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 2ff07b5 ("scsi: hisi_sas: Directly call register
snapshot instead of using workqueue") in v6.7-rc1.
Fixed in v6.9-rc1.

Fixed status
mainline: [3c4f53b2c341ec6428b98cb51a89a09b025d0953]
stable/6.8: [85c98073ffcfe9e46abfb9c66f3364467119d563]

CVE-2024-26874: drm/mediatek: Fix a null pointer crash in
mtk_drm_crtc_finish_page_flip

Announce: https://lore.kernel.org/linux-cve-announce/2024041739-CVE-2024-26874-79b0@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 119f517 ("drm/mediatek: Add DRM Driver for
Mediatek SoC MT8173.") in v4.7-rc1.
This commit is not backported to 4.4.
Fixed in v6.9-rc1.

Fixed status
mainline: [c958e86e9cc1b48cac004a6e245154dfba8e163b]
stable/4.19: [accdac6b71d5a2b84040c3d2234f53a60edc398e]
stable/5.10: [4688be96d20ffa49d2186523ee84f475f316fd49]
stable/5.15: [9beec711a17245b853d64488fd5b739031612340]
stable/5.4: [dfde84cc6c589f2a9f820f12426d97365670b731]
stable/6.1: [d2bd30c710475b2e29288827d2c91f9e6e2b91d7]
stable/6.6: [a3dd12b64ae8373a41a216a0b621df224210860a]
stable/6.8: [3fc88b246a2fc16014e374040fc15af1d3752535]

CVE-2024-26875: media: pvrusb2: fix uaf in pvr2_context_set_notify

Announce: https://lore.kernel.org/linux-cve-announce/2024041739-CVE-2024-26875-8394@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit e5be15c ("V4L/DVB (7711): pvrusb2: Fix race on
module unload") in v2.6.26-rc1.
Fixed in v6.9-rc1.

Fixed status
cip/4.4: [4bfc7ec23b25eced1a985408267fec015d497972]
cip/4.4-st: [4bfc7ec23b25eced1a985408267fec015d497972]
mainline: [0a0b79ea55de8514e1750884e5fec77f9fdd01ee]
stable/4.19: [ed8000e1e8e9684ab6c30cf2b526c0cea039929c]
stable/5.10: [ab896d93fd6a2cd1afeb034c3cc9226cb499209f]
stable/5.15: [eb6e9dce979c08210ff7249e5e0eceb8991bfcd7]
stable/5.4: [d29ed08964cec8b9729bc55c7bb23f679d7a18fb]
stable/6.1: [3a1ec89708d2e57e2712f46241282961b1a7a475]
stable/6.6: [8e60b99f6b7ccb3badeb512f5eb613ad45904592]
stable/6.8: [eaa410e05bdf562c90b23cdf2d9327f9c4625e16]

CVE-2024-26876: drm/bridge: adv7511: fix crash on irq during probe

Announce: https://lore.kernel.org/linux-cve-announce/2024041739-CVE-2024-26876-3948@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 3b1b975 ("drm: adv7511/33: add HDMI CEC support")
in v4.15-rc1.
This commit is not backported to 4.4.
Fixed in v6.9-rc1.

Fixed status
mainline: [aeedaee5ef5468caf59e2bb1265c2116e0c9a924]
stable/6.8: [28a94271bd50e4cf498df0381f776f8ea40a289e]

CVE-2024-26877: crypto: xilinx - call finalize with bh disabled

Announce: https://lore.kernel.org/linux-cve-announce/2024041739-CVE-2024-26877-72a3@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 4d96f7d ("crypto: xilinx - Add Xilinx AES
driver") in v5.7-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [a853450bf4c752e664abab0b2fad395b7ad7701c]
stable/5.10: [8a01335aedc50a66d04dd39203c89f4bc8042596]
stable/5.15: [03e6d4e948432a61b35783323b6ab2be071d2619]
stable/6.1: [a71f66bd5f7b9b35a8aaa49e29565eca66299399]
stable/6.6: [23bc89fdce71124cd2126fc919c7076e7cb489cf]
stable/6.8: [dbf291d8ffffb70f48286176a15c6c54f0bb0743]

CVE-2024-26878: quota: Fix potential NULL pointer dereference

Announce: https://lore.kernel.org/linux-cve-announce/2024041740-CVE-2024-26878-5748@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.9-rc1.
IT looks as if 4.4 is affected too.

Fixed status
mainline: [d0aa72604fbd80c8aabb46eda00535ed35570f1f]
stable/4.19: [8514899c1a4edf802f03c408db901063aa3f05a1]
stable/5.10: [61380537aa6dd32d8a723d98b8f1bd1b11d8fee0]
stable/5.15: [1ca72a3de915f87232c9a4cb9bebbd3af8ed3e25]
stable/5.4: [49669f8e7eb053f91d239df7b1bfb4500255a9d0]
stable/6.1: [7f9e833fc0f9b47be503af012eb5903086939754]
stable/6.6: [40a673b4b07efd6f74ff3ab60f38b26aa91ee5d5]
stable/6.8: [6afc9f4434fa8063aa768c2bf5bf98583aee0877]

CVE-2024-26879: clk: meson: Add missing clocks to axg_clk_regmaps

Announce: https://lore.kernel.org/linux-cve-announce/2024041740-CVE-2024-26879-e0d9@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 14ebb31 ("clk: meson: axg: add Video Clocks") in v5.11-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [ba535bce57e71463a86f8b33a0ea88c26e3a6418]
stable/5.15: [a03ed00787b0ce7a83eebabd0fa95ecc4a5cac84]
stable/6.1: [7ae1b0dc12ec407f12f80b49d22c6ad2308e2202]
stable/6.6: [0cbefc7b5bdad86b18a263d837450cdc9a56f8d7]
stable/6.8: [9f3e5df38b4528213449e55b80f0316864f2a1c8]

CVE-2024-26880: dm: call the resume method on internal suspend

Announce: https://lore.kernel.org/linux-cve-announce/2024041740-CVE-2024-26880-25d6@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit ffcc393 ("dm: enhance internal suspend and resume
interface") in v3.19-rc1.
Fixed in v6.9-rc1.

Fixed status
cip/4.4: [5b751acdbca079301db6ac4f8f7cfe95a3a38d58]
cip/4.4-st: [5b751acdbca079301db6ac4f8f7cfe95a3a38d58]
mainline: [65e8fbde64520001abf1c8d0e573561b4746ef38]
stable/4.19: [69836d9329f0b4c58faaf3d886a7748ddb5bf718]
stable/5.10: [f89bd27709376d37ff883067193320c58a8c1d5a]
stable/5.15: [03ad5ad53e51abf3a4c7538c1bc67a5982b41dc5]
stable/5.4: [da7ece2197101b1469853e6b5e915be1e3896d52]
stable/6.1: [ad10289f68f45649816cc68eb93f45fd5ec48a15]
stable/6.6: [15a3fc5c8774c17589dabfe1d642d40685c985af]
stable/6.8: [360a7d1be8112654f1fb328ed3862be630bca3f4]

CVE-2024-26881: net: hns3: fix kernel crash when 1588 is received on
HIP08 devices

Announce: https://lore.kernel.org/linux-cve-announce/2024041740-CVE-2024-26881-ffd3@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 0bf5eb7 ("net: hns3: add support for PTP") in v5.14-rc1.
Fixed in v6.9-rc1.

Fixed status
mainline: [0fbcf2366ba9888cf02eda23e35fde7f7fcc07c3]
stable/5.15: [23ec1cec24293f9799c725941677d4e167997265]
stable/6.1: [b3cf70472a600bcb2efe24906bc9bc6014d4c6f6]
stable/6.6: [f0b5225a7dfc1bf53c98215db8c2f0b4efd3f108]
stable/6.8: [11b998360d96f6c76f04a95f54b49f24d3c858e4]

CVE-2024-26882: net: ip_tunnel: make sure to pull inner header in
ip_tunnel_rcv()

Announce: https://lore.kernel.org/linux-cve-announce/2024041741-CVE-2024-26882-be35@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit c544193 ("GRE: Refactor GRE tunneling code.") in v3.10-rc1.
Fixed in v6.9-rc1.

Fixed status
mainline: [b0ec2abf98267f14d032102551581c833b0659d3]
stable/5.10: [77fd5294ea09b21f6772ac954a121b87323cec80]
stable/5.15: [5c03387021cfa3336b97e0dcba38029917a8af2a]
stable/5.4: [ec6bb01e02cbd47781dd90775b631a1dc4bd9d2b]
stable/6.1: [60044ab84836359534bd7153b92e9c1584140e4a]
stable/6.6: [c4c857723b37c20651300b3de4ff25059848b4b0]
stable/6.8: [ca914f1cdee8a85799942c9b0ce5015bbd6844e1]

CVE-2024-26883: bpf: Fix stackmap overflow check on 32-bit arches

Announce: https://lore.kernel.org/linux-cve-announce/2024041741-CVE-2024-26883-1fc4@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 6183f4d ("bpf: Check for integer overflow when
using roundup_pow_of_two()") in v5.11.
This commit is backported to 4.19, 5.10, and 5.4.
Fixed in v6.9-rc1.

Fixed status
mainline: [7a4b21250bf79eef26543d35bd390448646c536b]
stable/4.19: [d0e214acc59145ce25113f617311aa79dda39cb3]
stable/5.10: [15641007df0f0d35fa28742b25c2a7db9dcd6895]
stable/5.15: [ca1f06e72dec41ae4f76e7b1a8a97265447b46ae]
stable/5.4: [21e5fa4688e1a4d3db6b72216231b24232f75c1d]
stable/6.1: [f06899582ccee09bd85d0696290e3eaca9aa042d]
stable/6.6: [7070b274c7866a4c5036f8d54fcaf315c64ac33a]
stable/6.8: [0971126c8164abe2004b8536b49690a0d6005b0a]

CVE-2024-26884: bpf: Fix hashtab overflow check on 32-bit arches

Announce: https://lore.kernel.org/linux-cve-announce/2024041741-CVE-2024-26884-433b@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit daaf427 ("bpf: fix arraymap NULL deref and
missing overflow and zero size checks") in v3.19-rc1.
Fixed in v6.9-rc1.

Fixed status
mainline: [6787d916c2cf9850c97a0a3f73e08c43e7d973b1]
stable/4.19: [33ec04cadb77605b71d9298311919303d390c4d5]
stable/5.10: [64f00b4df0597590b199b62a37a165473bf658a6]
stable/5.15: [3b08cfc65f07b1132c1979d73f014ae6e04de55d]
stable/5.4: [92c81fbb3ed2e0dfc33a4183a67135e1ab566ace]
stable/6.1: [a83fdaeaea3677b83a53f72ace2d73a19bcd6d93]
stable/6.6: [8435f0961bf3dc65e204094349bd9aeaac1f8868]
stable/6.8: [a6fa75b5096c0f9826a4fabe22d907b0a5bb1016]

CVE-2024-26885: bpf: Fix DEVMAP_HASH overflow check on 32-bit arches

Announce: https://lore.kernel.org/linux-cve-announce/2024041741-CVE-2024-26885-4224@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 6f9d451 ("xdp: Add devmap_hash map type for
looking up devices by hashed index") in v5.4-rc1.
Fixed in v6.9-rc1.

Fixed status
mainline: [281d464a34f540de166cee74b723e97ac2515ec3]
stable/5.10: [225da02acdc97af01b6bc6ce1a3e5362bf01d3fb]
stable/5.15: [c826502bed93970f2fd488918a7b8d5f1d30e2e3]
stable/6.1: [edf7990baa48de5097daa9ac02e06cb4c798a737]
stable/6.6: [250051acc21f9d4c5c595e4fcb55986ea08c4691]
stable/6.8: [e89386f62ce9a9ab9a94835a9890883c23d9d52c]

CVE-2024-26886: Bluetooth: af_bluetooth: Fix deadlock

Announce: https://lore.kernel.org/linux-cve-announce/2024041742-CVE-2024-26886-6345@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 2e07e83 ("Bluetooth: af_bluetooth: Fix
Use-After-Free in bt_sock_recvmsg") in v6.7-rc7.
This commit was backported to 5.10, 5.15, 6.1, and 6.6.
Fixed in v6.9-rc1.

Fixed status
mainline: [f7b94bdc1ec107c92262716b073b3e816d4784fb]
stable/6.1: [cb8adca52f306563d958a863bb0cbae9c184d1ae]
stable/6.6: [64be3c6154886200708da0dfe259705fb992416c]
stable/6.8: [2c9e2df022ef8b9d7fac58a04a2ef4ed25288955]

CVE-2024-26887: Bluetooth: btusb: Fix memory leak

Announce: https://lore.kernel.org/linux-cve-announce/2024041742-CVE-2024-26887-1126@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 0b70151 ("Bluetooth: btusb: mediatek: add
MediaTek devcoredump support") in v6.6-rc1.
Fixed in v6.9-rc1.

Fixed status
mainline: [79f4127a502c5905f04da1f20a7bbe07103fb77c]
stable/6.6: [620b9e60e4b55fa55540ce852a0f3c9e6091dbbc]
stable/6.8: [b08bd8f02a24e2b82fece5ac51dc1c3d9aa6c404]

CVE-2024-26888: Bluetooth: msft: Fix memory leak

Announce: https://lore.kernel.org/linux-cve-announce/2024041742-CVE-2024-26888-48e6@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 9e14606 ("Bluetooth: msft: Extended monitor
tracking by address filter") in v6.6-rc1.
Fixed in v6.9-rc1.

Fixed status
mainline: [a6e06258f4c31eba0fcd503e19828b5f8fe7b08b]
stable/6.6: [98e9920c75e0790bff947a00d192d24bf1c724e0]
stable/6.8: [5cb93417c93716a5404f762f331f5de3653fd952]

CVE-2024-26889: Bluetooth: hci_core: Fix possible buffer overflow

Announce: https://lore.kernel.org/linux-cve-announce/2024041742-CVE-2024-26889-edfc@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit dcda165 ("Bluetooth: hci_core: Fix build
warnings") in v6.6-rc5.
Fixed in v6.9-rc1.

Fixed status
cip/4.4: [80dde49b8ca7bff8e943ebd29a790ec4dcf2ec29]
cip/4.4-st: [80dde49b8ca7bff8e943ebd29a790ec4dcf2ec29]
mainline: [81137162bfaa7278785b24c1fd2e9e74f082e8e4]
stable/4.19: [6d5a9d4a7bcbb7534ce45a18a52e7bd23e69d8ac]
stable/5.10: [d47e6c1932cee02954ea588c9f09fd5ecefeadfc]
stable/5.15: [2e845867b4e279eff0a19ade253390470e07e8a1]
stable/5.4: [54a03e4ac1a41edf8a5087bd59f8241b0de96d3d]
stable/6.1: [68644bf5ec6baaff40fc39b3529c874bfda709bd]
stable/6.6: [a41c8efe659caed0e21422876bbb6b73c15b5244]
stable/6.8: [2edce8e9a99dd5e4404259d52e754fdc97fb42c2]

CVE-2024-26890: Bluetooth: btrtl: fix out of bounds memory access

Announce: https://lore.kernel.org/linux-cve-announce/2024041742-CVE-2024-26890-4239@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 5b35594 ("Bluetooth: btrtl: Add btrealtek data
struct") in v6.2-rc1.
Introduced by commit 044014c ("Bluetooth: btrtl: Add Realtek
devcoredump support") in v6.6-rc1.
Fixed in v6.9-rc1.

Fixed status
mainline: [de4e88ec58c4202efd1f02eebb4939bbf6945358]
stable/6.6: [dd163fa34c483f1674aa2510accce11a224f649e]
stable/6.8: [0c657e641df1e77d6087688190f632cad9c0439b]

CVE-2024-26891: iommu/vt-d: Don't issue ATS Invalidation request when
device is disconnected

Announce: https://lore.kernel.org/linux-cve-announce/2024041743-CVE-2024-26891-940d@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 6f7db75 ("iommu/vt-d: Add second level page table
interface") in v5.0-rc1.
Fixed in v6.9-rc1.

Fixed status
mainline: [4fc82cd907ac075648789cc3a00877778aa1838b]
stable/5.10: [f873b85ec762c5a6abe94a7ddb31df5d3ba07d85]
stable/5.15: [d70f1c85113cd8c2aa8373f491ca5d1b22ec0554]
stable/6.1: [34a7b30f56d30114bf4d436e4dc793afe326fbcf]
stable/6.6: [2b74b2a92e524d7c8dec8e02e95ecf18b667c062]
stable/6.8: [025bc6b41e020aeb1e71f84ae3ffce945026de05]

CVE-2024-26892: wifi: mt76: mt7921e: fix use-after-free in free_irq()

Announce: https://lore.kernel.org/linux-cve-announce/2024041743-CVE-2024-26892-809e@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 9270270 ("wifi: mt76: mt7921: fix PCI DMA hang
after reboot") in v6.4-rc1.
Fixed in v6.9-rc1.

Fixed status
mainline: [c957280ef6ab6bdf559a91ae693a6b34310697e3]
stable/6.6: [c7dd42fbebcfb02bef070fd48f774d6412d0b49d]
stable/6.8: [bfeaef901194c5923ce3330272786eff2fac513a]

CVE-2024-26893: firmware: arm_scmi: Fix double free in SMC transport
cleanup path

Announce: https://lore.kernel.org/linux-cve-announce/2024041743-CVE-2024-26893-34df@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 1dc6558 ("firmware: arm_scmi: Add smc/hvc
transport") in v5.8-rc1.
Fixed in v6.9-rc1.

Fixed status
mainline: [f1d71576d2c9ec8fdb822173fa7f3de79475e9bd]
stable/6.1: [0d276d9f335f41d6524258d58c0c0241ef9a83a4]
stable/6.6: [857f56db8c3a71f9871922b6984ff74ad588cb2c]
stable/6.8: [ead445dd3d681020af333649a27306160eee761d]

CVE-2024-26894: ACPI: processor_idle: Fix memory leak in
acpi_processor_power_exit()

Announce: https://lore.kernel.org/linux-cve-announce/2024041743-CVE-2024-26894-53ad@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 3d339dc ("cpuidle / ACPI : move cpuidle_device
field out of the acpi_processor_power structure") in v3.7-rc1.
Fixed in v6.9-rc1.

Fixed status
cip/4.4: [4ee875ed7f4b1a278bde5af653d1fa2ea962ff1b]
cip/4.4-st: [4ee875ed7f4b1a278bde5af653d1fa2ea962ff1b]
mainline: [e18afcb7b2a12b635ac10081f943fcf84ddacc51]
stable/4.19: [d351bcadab6caa6d8ce7159ff4b77e2da35c09fa]
stable/5.10: [c2a30c81bf3cb9033fa9f5305baf7c377075e2e5]
stable/5.15: [1cbaf4c793b0808532f4e7b40bc4be7cec2c78f2]
stable/5.4: [ea96bf3f80625cddba1391a87613356b1b45716d]
stable/6.1: [fad9bcd4d754cc689c19dc04d2c44b82c1a5d6c8]
stable/6.6: [3d48e5be107429ff5d824e7f2a00d1b610d36fbc]
stable/6.8: [cd5c2d0b09d5b6d3f0a7bbabe6761a4997e9dee9]

CVE-2024-26895: wifi: wilc1000: prevent use-after-free on vif when
cleaning up all interfaces

Announce: https://lore.kernel.org/linux-cve-announce/2024041744-CVE-2024-26895-5eee@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 8399918 ("staging: wilc1000: use RCU list to
maintain vif interfaces list") in v5.5-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [cb5942b77c05d54310a0420cac12935e9b6aa21c]
stable/5.10: [5956f4203b6cdd0755bbdd21b45f3933c7026208]
stable/5.15: [fe20e3d56bc911408fc3c27a17c59e9d7885f7d1]
stable/6.1: [a9545af2a533739ffb64d6c9a6fec6f13e2b505f]
stable/6.6: [3da9d32b7f4a1a9f7e4bb15bb82f2b2dd6719447]
stable/6.8: [73a2aa0aef86c2c07be5a2f42c9e6047e1a2f7bb]

CVE-2024-26896: wifi: wfx: fix memory leak when starting AP

Announce: https://lore.kernel.org/linux-cve-announce/2024041744-CVE-2024-26896-79fe@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 268bcee ("staging: wfx: fix BA when device is AP
and MFP is enabled") in v5.10-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [b8cfb7c819dd39965136a66fe3a7fde688d976fc]
stable/6.1: [a1f57a0127b89a6b6620514564aa7eaec16d9af3]
stable/6.6: [3a71ec74e5e3478d202a1874f085ca3ef40be49b]
stable/6.8: [dadbb5d29d6c5f571a50272fce8c1505a9559487]

CVE-2024-26897: wifi: ath9k: delay all of ath9k_wmi_event_tasklet()
until init is complete

Announce: https://lore.kernel.org/linux-cve-announce/2024041744-CVE-2024-26897-5382@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 8b3046a ("ath9k_htc: fix NULL pointer dereference
at ath9k_htc_tx_get_packet()") in v5.17-rc1.
This commit was backported to 5.10 and 5.15.
Fixed in v6.9-rc1.

Fixed status
mainline: [24355fcb0d4cbcb6ddda262596558e8cfba70f11]
stable/5.10: [1bc5461a21c56a36e2a7d81e152b90ce019a3905]
stable/5.15: [f8ff4b4df71e87f609be0cc37d92e918107f9b90]
stable/6.1: [74d0639261dd795dce958d1b14815bdcbb48a715]
stable/6.6: [a015fbf698c8957aa5fbeefc5c59dd2cf3107298]
stable/6.8: [4afa0246656d5680c8a4c3fb37ba6570c4ab819b]

CVE-2024-26898: aoe: fix the potential use-after-free problem in aoecmd_cfg_pkts

Announce: https://lore.kernel.org/linux-cve-announce/2024041744-CVE-2024-26898-d199@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 7562f87 ("[NET]: Rework dev_base via list_head
(v3)") in v2.6.22-rc1.
Fixed in v6.9-rc1.

Fixed status
cip/4.4: [dd4e20bd656b6a9618e60d86bdefc0f3db636f22]
cip/4.4-st: [dd4e20bd656b6a9618e60d86bdefc0f3db636f22]
mainline: [f98364e926626c678fb4b9004b75cacf92ff0662]
stable/4.19: [ad80c34944d7175fa1f5c7a55066020002921a99]
stable/5.10: [faf0b4c5e00bb680e8e43ac936df24d3f48c8e65]
stable/5.15: [7dd09fa80b0765ce68bfae92f4e2f395ccf0fba4]
stable/5.4: [1a54aa506b3b2f31496731039e49778f54eee881]
stable/6.1: [74ca3ef68d2f449bc848c0a814cefc487bf755fa]
stable/6.6: [eb48680b0255a9e8a9bdc93d6a55b11c31262e62]
stable/6.8: [a16fbb80064634b254520a46395e36b87ca4731e]

CVE-2024-26899: block: fix deadlock between bd_link_disk_holder and
partition scan

Announce: https://lore.kernel.org/linux-cve-announce/2024041745-CVE-2024-26899-3f41@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 1b0a2d9 ("md: use new apis to suspend array for
ioctls involed array reconfiguration") in v6.7-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [03f12122b20b6e6028e9ed69030a49f9cffcbb75]
stable/6.8: [5a87c1f7993bc8ac358a3766bac5dc7126e01e98]

CVE-2024-26900: md: fix kmemleak of rdev->serial

Announce: https://lore.kernel.org/linux-cve-announce/2024041745-CVE-2024-26900-70a3@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 963c555 ("md: introduce
mddev_create/destroy_wb_pool for the change of member device") in
v5.3-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc1.

Fixed status
mainline: [6cf350658736681b9d6b0b6e58c5c76b235bb4c4]
stable/6.8: [4c1021ce46fc2fb6115f7e79d353941e6dcad366]

CVE-2024-26901: do_sys_name_to_handle(): use kzalloc() to fix kernel-infoleak

Announce: https://lore.kernel.org/linux-cve-announce/2024041745-CVE-2024-26901-34e7@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 990d6c2 ("vfs: Add name to file handle conversion
support") in v2.6.39-rc1.
Fixed in v6.9-rc1.

Fixed status
cip/4.4: [3f84230ccc80aeb6cbddcbd5f8f519251055c8bd]
cip/4.4-st: [3f84230ccc80aeb6cbddcbd5f8f519251055c8bd]
mainline: [3948abaa4e2be938ccdfc289385a27342fb13d43]
stable/4.19: [4bac28f441e3cc9d3f1a84c8d023228a68d8a7c1]
stable/5.10: [cde76b3af247f615447bcfecf610bb76c3529126]
stable/5.15: [423b6bdf19bbc5e1f7e7461045099917378f7e71]
stable/5.4: [772a7def9868091da3bcb0d6c6ff9f0c03d7fa8b]
stable/6.1: [e6450d5e46a737a008b4885aa223486113bf0ad6]
stable/6.6: [c1362eae861db28b1608b9dc23e49634fe87b63b]
stable/6.8: [bf9ec1b24ab4e94345aa1c60811dd329f069c38b]

CVE-2024-26902: perf: RISCV: Fix panic on pmu overflow handler

Announce: https://lore.kernel.org/linux-cve-announce/2024041745-CVE-2024-26902-5f77@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc7.
Affected file drivers/perf/riscv_pmu_sbi.c was introduced by commit
e9991434 ("RISC-V: Add perf platform driver based on SBI PMU
extension") in 5.18-rc1.
The pmu_sbi_set_scounteren() and pmu_sbi_reset_scounteren() was
vulnerable since commit cc4c07c89 ("drivers: perf: Implement perf
event mmap support in the SBI backend") in 6.6-rc1.
The pmu_sbi_ovf_handler() was vulnerable since commit 4905ec2fb
("RISC-V: Add sscofpmf extension support") in 5.18-rc1.

Fixed status
mainline: [34b567868777e9fd39ec5333969728a7f0cf179c]
stable/6.6: [3ede8e94de6b834b48b0643385e66363e7a04be9]

CVE-2024-26903: Bluetooth: rfcomm: Fix null-ptr-deref in rfcomm_check_security

Announce: https://lore.kernel.org/linux-cve-announce/2024041745-CVE-2024-26903-de5c@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc7.

Fixed status
cip/4.4: [7e4e21f7b33e0c5bdcd99a981826cccaaf465456]
cip/4.4-st: [7e4e21f7b33e0c5bdcd99a981826cccaaf465456]
mainline: [2535b848fa0f42ddff3e5255cf5e742c9b77bb26]
stable/4.19: [369f419c097e82407dd429a202cde9a73d3ae29b]
stable/5.10: [81d7d920a22fd58ef9aedb1bd0a68ee32bd23e96]
stable/5.15: [8d1753973f598531baaa2c1033cf7f7b5bb004b0]
stable/5.4: [5f369efd9d963c1f711a06c9b8baf9f5ce616d85]
stable/6.1: [567c0411dc3b424fc7bd1e6109726d7ba32d4f73]
stable/6.6: [3ead59bafad05f2967ae2438c0528d53244cfde5]

CVE-2024-26904: btrfs: fix data race at btrfs_use_block_rsv() when
accessing block reserve

Announce: https://lore.kernel.org/linux-cve-announce/2024041746-CVE-2024-26904-e3a8@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc7.
It seems as if all stable kernels are affected.
The btrfs_use_block_rsv() was renamed from use_block_rsv() by commit
67f9c220 ("btrfs: migrate the global_block_rsv helpers to
block-rsv.c") in 5.3-rc1.

Fixed status
mainline: [c7bb26b847e5b97814f522686068c5628e2b3646]
stable/5.4: [2daa2a8e895e6dc2395f8628c011bcf1e019040d]
stable/6.1: [ab1be3f1aa7799f99155488c28eacaef65eb68fb]
stable/6.6: [f6d4d29a12655b42a13cec038c2902bb7efc50ed]

CVE-2024-26905: btrfs: fix data races when accessing the reserved
amount of block reserves

Announce: https://lore.kernel.org/linux-cve-announce/2024041746-CVE-2024-26905-69f0@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc7.
The global_rsv_size was introduced in need_preemptive_reclaim() since
commit 610a6ef44 ("btrfs: take into account global rsv in
need_preemptive_reclaim") in 5.14-rc1.
The global_rsv_size was introduced in
btrfs_preempt_reclaim_metadata_space() since commit 576fa348 ("btrfs:
improve preemptive background space flushing") in 5.12-rc1-dontuse.
So, it seems as if prior to 5.12 kernels are not affected.

Fixed status
mainline: [e06cc89475eddc1f3a7a4d471524256152c68166]
stable/6.1: [995e91c9556c8fc6028b474145a36e947d1eb6b6]
stable/6.6: [82220b1835baaebf4ae2e490f56353a341a09bd2]

CVE-2024-26906: x86/mm: Disallow vsyscall page read for
copy_from_kernel_nofault()

Announce: https://lore.kernel.org/linux-cve-announce/2024041746-CVE-2024-26906-bb35@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc6.
Affected file arch/x86/mm/maccess.c was introduced by commit 75a1a607b
("uaccess: Add strict non-pagefault kernel-space read function") in
5.5-rc1.
Therefore, prior to 5.5 kernels are not affected.

Fixed status
mainline: [32019c659ecfe1d92e3bf9fcdfbb11a7c70acd58]
stable/5.10: [6e4694e65b6db4c3de125115dd4f55848cc48381]
stable/5.15: [e8a67fe34b76a49320b33032228a794f40b0316b]
stable/6.1: [f175de546a3eb77614d94d4c02550181c0a8493e]
stable/6.6: [57f78c46f08198e1be08ffe99c4c1ccc12855bf5]

CVE-2024-26907: RDMA/mlx5: Fix fortify source warning while accessing
Eth segment

Announce: https://lore.kernel.org/linux-cve-announce/2024041746-CVE-2024-26907-a02d@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc6.
The set_eth_seg() was introduced by commit f0313965 ("IB/mlx5:
Implement UD QP offloads for IPoIB in the TX flo") in 4.6-rc1.
So, 4.4 is not affected.
Using memcpy() as "memcpy(eseg->inline_hdr.start, pdata, copysz);" was
introduced by commit 34f4c955 ("IB/mlx5: Use fragmented QP's buffer
for in-kernel users") in 5.0-rc1.
It replaced "memcpy(seg - size_of_inl_hdr_start, pdata, copysz);".

Fixed status
mainline: [4d5e86a56615cc387d21c629f9af8fb0e958d350]
stable/5.10: [d27c48dc309da72c3b46351a1205d89687272baa]
stable/5.15: [60ba938a8bc8c90e724c75f98e932f9fb7ae1b9d]
stable/6.1: [cad82f1671e41094acd3b9a60cd27d67a3c64a21]
stable/6.6: [9a624a5f95733bac4648ecadb320ca83aa9c08fd]

CVE-2024-26908: x86/xen: Add some null pointer checking to smp.c

Announce: https://lore.kernel.org/linux-cve-announce/2024041747-CVE-2024-26908-4690@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc5.

Fixed status
cip/4.4: [2cdf6485e8f1aec725fa4f12ddf16be3317755d8]
cip/4.4-st: [2cdf6485e8f1aec725fa4f12ddf16be3317755d8]
mainline: [3693bb4465e6e32a204a5b86d3ec7e6b9f7e67c2]
stable/4.19: [70a33a629090130d731fc1e1ad498bb672eea165]
stable/5.10: [eb279074badac0bbe28749906562d648ca4bc750]
stable/5.15: [8082bccb7ac480ceab89b09c53d20c78ae54f9fa]
stable/5.4: [025a8a96c7ef3ff24a9b4753a7e851ba16f11bfc]
stable/6.1: [f49c513f46dc19bf01ffad2aaaf234d7f37f6799]
stable/6.6: [a9bbb05c0c04b49a1f7f05fd03826321dca2b8d4]

CVE-2024-26909: soc: qcom: pmic_glink_altmode: fix drm bridge use-after-free

Announce: https://lore.kernel.org/linux-cve-announce/2024041747-CVE-2024-26909-d9d0@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 080b4e2 ("soc: qcom: pmic_glink: Introduce
altmode support") in v6.3-rc1.
Introduced by commit 2bcca96 ("soc: qcom: pmic-glink: switch to
DRM_AUX_HPD_BRIDGE") in v6.8-rc1.
These commits are not backportedt to older stable kernels.
Fixed in v6.8-rc7.

Fixed status
mainline: [b979f2d50a099f3402418d7ff5f26c3952fb08bb]
stable/6.6: [2bbd65c6ca567ed8dbbfc4fb945f57ce64bef342]

CVE-2024-26910: netfilter: ipset: fix performance regression in swap operation

Announce: https://lore.kernel.org/linux-cve-announce/2024041736-CVE-2024-26910-3617@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 28628fa ("netfilter: ipset: fix race condition
between swap/destroy and kernel side add/del/test") in v6.7-rc2.
This commit was backported to 4.19, 5.10, 5.15, 5.4, 6.1, and 6.6.
Fixed in v6.8-rc3.

Fixed status
mainline: [97f7cf1cd80eeed3b7c808b7c12463295c751001]
stable/5.10: [a24d5f2ac8ef702a58e55ec276aad29b4bd97e05]
stable/5.15: [c2dc077d8f722a1c73a24e674f925602ee5ece49]
stable/5.4: [c7f2733e5011bfd136f1ca93497394d43aa76225]
stable/6.1: [653bc5e6d9995d7d5f497c665b321875a626161c]
stable/6.6: [b93a6756a01f4fd2f329a39216f9824c56a66397]

CVE-2024-26911: drm/buddy: Fix alloc_range() error handling code

Announce: https://lore.kernel.org/linux-cve-announce/2024041736-CVE-2024-26911-e758@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 0a1844b ("drm/buddy: Improve contiguous memory
allocation") in v6.7-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc5.

Fixed status
mainline: [8746c6c9dfa31d269c65dd52ab42fde0720b7d91]

CVE-2024-26912: drm/nouveau: fix several DMA buffer leaks

Announce: https://lore.kernel.org/linux-cve-announce/2024041736-CVE-2024-26912-9206@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 176fdcb ("drm/nouveau/gsp/r535: add support for
booting GSP-RM") in v6.7-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc4.

Fixed status
mainline: [042b5f83841fbf7ce39474412db3b5e4765a7ea7]

CVE-2024-26913: drm/amd/display: Fix dcn35 8k30 Underflow/Corruption Issue

Announce: https://lore.kernel.org/linux-cve-announce/2024041736-CVE-2024-26913-2cb3@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc3.
The get_scaler_data_for_plane() was introduced by commit 7966f319
("drm/amd/display: Introduce DML2") in 6.7-rc1.

Fixed status
mainline: [faf51b201bc42adf500945732abb6220c707d6f3]

CVE-2024-26914: drm/amd/display: fix incorrect mpc_combine array size

Announce: https://lore.kernel.org/linux-cve-announce/2024041737-CVE-2024-26914-e47b@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc3.
It looks it was introduced by commit c51d872 ("drm/amd/display: do not
attempt ODM power optimization if minimal transition doesn't exist")
in 6.7-rc1.
Fixed status
mainline: [39079fe8e660851abbafa90cd55cbf029210661f]

CVE-2024-26915: drm/amdgpu: Reset IH OVERFLOW_CLEAR bit

Announce: https://lore.kernel.org/linux-cve-announce/2024041737-CVE-2024-26915-112b@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc3.

Fixed status
mainline: [7330256268664ea0a7dd5b07a3fed363093477dd]
stable/5.15: [9a9d00c23d170d4ef5a1b28e6b69f5c85dd12bc1]
stable/6.1: [a28f4d1e0bed85943d309ac243fd1c200f8af9a2]
stable/6.6: [8983397951b4b0bd51bb4b4ba9749424e1ccbb70]

CVE-2024-26916: Revert "drm/amd: flush any delayed gfxoff on suspend entry"

Announce: https://lore.kernel.org/linux-cve-announce/2024041737-CVE-2024-26916-4a45@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit ab47503 ("drm/amdgpu/sdma5.2: add begin/end_use
ring callbacks") in v6.7-rc6.
It looks as if all stable kernels are affected.

The cik_ih.c, cik_ih.c, iceland_ih.c, and tonga_ih.c were introduced in 4.2-rc1.
The ih_v6_0.c was intrduced in 5.19-rc1.
The ih_v6_1.c was introduced in 6.6-rc1.
The navi10_ih.c was introduced in 5.3-rc1.
The si_ih.c was introduced in 4.9-rc1.
The vega10_ih.c was introduced in 4.12-rc1.
The vega20_ih.c was introduced in 5.12-rc1-dontuse.

Fixed in v6.8-rc5.

Fixed status
mainline: [916361685319098f696b798ef1560f69ed96e934]
stable/5.15: [65158edb0a3a8df23197d52cd24287e39eaf95d6]
stable/6.1: [ff70e6ff6fc2413caf33410af7462d1f584d927e]
stable/6.6: [caa2565a2e13899be31f7b1e069e6465d3e2adb0]

CVE-2024-26917: scsi: Revert "scsi: fcoe: Fix potential deadlock on
&fip->ctlr_lock"

Announce: https://lore.kernel.org/linux-cve-announce/2024041737-CVE-2024-26917-8eda@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 1a19755 ("scsi: fcoe: Fix potential deadlock on
&fip->ctlr_lock") in v6.6-rc1.
Fixed in v6.8-rc5.

Fixed status
cip/4.4: [63aab4c4ce32ca02703b2ac8e5820dc7d1c4b28b]
cip/4.4-rt: [63aab4c4ce32ca02703b2ac8e5820dc7d1c4b28b]
cip/4.4-st: [63aab4c4ce32ca02703b2ac8e5820dc7d1c4b28b]
mainline: [977fe773dcc7098d8eaf4ee6382cb51e13e784cb]
stable/4.19: [94a600226b6d0ef065ee84024b450b566c5a87d6]
stable/5.10: [7d4e19f7ff644c5b79e8271df8ac2e549b436a5b]
stable/5.15: [5b8f473c4de95c056c1c767b1ad48c191544f6a5]
stable/5.4: [2209fc6e3d7727d787dc6ef9baa1e9eae6b1295b]
stable/6.1: [6bb22ac1d11d7d20f91e7fd2e657a9e5f6db65e0]
stable/6.6: [2996c7e97ea7cf4c1838a1b1dbc0885934113783]

CVE-2024-26918: PCI: Fix active state requirement in PME polling

Announce: https://lore.kernel.org/linux-cve-announce/2024041738-CVE-2024-26918-6767@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit d3fcd73 ("PCI: Fix runtime PM race with PME
polling") in v6.6-rc1.
Fixed in v6.8-rc5.

Fixed status
mainline: [41044d5360685e78a869d40a168491a70cdb7e73]
stable/6.6: [63b1a3d9dd3b3f6d67f524e76270e66767090583]

CVE-2024-26919: usb: ulpi: Fix debugfs directory leak

Announce: https://lore.kernel.org/linux-cve-announce/2024041738-CVE-2024-26919-5100@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit bd0a0a0 ("usb: ulpi: Add debugfs support") in v5.18-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc3.

Fixed status
mainline: [3caf2b2ad7334ef35f55b95f3e1b138c6f77b368]
stable/6.1: [d31b886ed6a5095214062ee4fb55037eb930adb6]
stable/6.6: [330d22aba17a4d30a56f007d0f51291d7e00862b]

CVE-2024-26920: tracing/trigger: Fix to return error if failed to alloc snapshot

Announce: https://lore.kernel.org/linux-cve-announce/2024041738-CVE-2024-26920-a681@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 0bbe7f7 ("tracing: Fix the race between
registering 'snapshot' event trigger and triggering 'snapshot'
operation") in v5.7-rc2.
This commit was backported to older stable kernels.
Fixed in v6.8-rc3.

Fixed status
cip/4.4: [a906faff69366bb6fb3b5d33dc7fcb7213e3c2d5]
cip/4.4-rt: [a906faff69366bb6fb3b5d33dc7fcb7213e3c2d5]
cip/4.4-st: [a906faff69366bb6fb3b5d33dc7fcb7213e3c2d5]
mainline: [0958b33ef5a04ed91f61cef4760ac412080c4e08]
stable/4.19: [bcf4a115a5068f3331fafb8c176c1af0da3d8b19]
stable/5.10: [56cfbe60710772916a5ba092c99542332b48e870]
stable/5.15: [b5085b5ac1d96ea2a8a6240f869655176ce44197]
stable/5.4: [8ffd5590f4d6ef5460acbeac7fbdff7025f9b419]
stable/6.1: [36be97e9eb535fe3008a5cb040b1e56f29f2e398]
stable/6.6: [6022c065c9ec465d84cebff8f480db083e4ee06b]

* Updated CVEs

CVE-2024-25739: Check for too small LEB size in VTBL code

The mainline, cip/4.4, cip/4.4-st, 5.15, 6.1, 6.6, and 6.8 were fixed.

Fixed status
cip/4.4: [42cee143e393919d1e983ac044efb8b0a6838bf0]
cip/4.4-st: [42cee143e393919d1e983ac044efb8b0a6838bf0]
mainline: [68a24aba7c593eafa8fd00f2f76407b9b32b47a9]
stable/5.15: [8ce982285414b741e2dd6ebb5a62e79dede44f7f]
stable/6.1: [5ecbc7465f66bb7eb2be2cd423f84000872e3560]
stable/6.6: [d1b505c988b711673d6a2de35222028be081d0d1]
stable/6.8: [04c4f2394970fa640bc794d627fe6b9406285406]

CVE-2024-24859: Race condition bug in sniff_{min,max}_interval_set()
in bluetooth driver causes DoS

The mainline, 5.15, 6.1, 6.6, and 6.8 were fixed.

Fixed status
mainline: [7835fcfd132eb88b87e8eb901f88436f63ab60f7]
stable/5.15: [a8170af8b10e904c0052aa4ec31c653635730d92]
stable/6.1: [18e189442a5896255e764f8e875c13d16248ef2f]
stable/6.6: [d75632d0db3cdc31873d25756066a7f56bc87737]
stable/6.8: [d0bfebd8ca411697248d0cebe4ad2649f23ab0bf]

CVE-2023-24023: A man-in-the-middle attacks was found in Bluetooth
Core Specification 4.2 through 5.4

The mainline, 6.1, and 6.6 were fixed.

Fixed status
mainline: [04a342cc49a8522e99c9b3346371c329d841dcd2]
stable/6.1: [0f7bffd40a517660853ebdc1a104bd493e6bbe4f]
stable/6.6: [34c032a72f97e05cd1388aaeb1b3b255ac3c9581]

CVE-2022-48627: vt: fix memory overlapping when deleting chars in the buffer

stable 4.19 and 5.4 were fixed.

Fixed status
mainline: [39cdb68c64d84e71a4a717000b6e5de208ee60cc]
stable/4.19: [c8686c014b5e872ba7e334f33ca553f14446fc29]
stable/5.10: [bfee93c9a6c395f9aa62268f1cedf64999844926]
stable/5.15: [57964a5710252bc82fe22d9fa98c180c58c20244]
stable/5.4: [815be99d934e3292906536275f2b8d5131cdf52c]

CVE-2023-28746:

stable 5.10 was fixed.

Fixed status
mainline: [e95df4ec0c0c9791941f112db699fae794b9862a,
4e42765d1be01111df0c0275bbaf1db1acef346e,
  8076fcde016c9c0e0660543e67bff86cb48a7c9c,
2a0180129d726a4b953232175857d442651b55a0]
stable/5.10: [6e04cae36b8f52c81cbcafdb8f198d80739943f1,
5fbd9f6c3953215923b8b4116e2d2b8dc4960d9f,
  66d5260fc7d5adb115c97f0e011ee13c0caa8ea6,
91cf85f75375359b73cd78a47cf1d6d50ec5e4b8]
stable/5.15: [a2b586df5546311f9be5f6acb9fe489b623c526e,
4fa001418efd40ad00ff429e6064ab8eeeddc739,
  2fb08b672eb78c4930413cf529734792456ae15f,
2ae88e83f3b7e579a7085d140f61122f128932f1]
stable/6.1: [8b5760939db9c49c03b9e19f6c485a8812f48d83,
29476fac750dddeabc3503bf9b13e05b949d7adb,
  d405b9c03f06b1b5e73ebc4f34452687022f7029,
b2e92ab17e440a97c716b701ecd897eebca11ac0]
stable/6.6: [c35ca0968de41952af2ad7d22881e4a7c6e1b145,
ddfd38558acc5b3891fd197372fedb76372da740,
  77018fb9efe50cf24e61275ee09253cf1fbb6854,
4a5b5bfea063745471af6395d22ebaea8242225e]
stable/6.7: [18867a204511d032c2a6ed083461a10905061fac,
13acf9f1df3513ea7a5170399c2a8e297e5fbdc1,
  fe5f4d14cdad934c5c92080cebd5b18189bf4ac9,
328607cf9e1fcbbc3f5521391d601306f72a5890]
stable/6.8: [056c33c67a74aec19668b927d460825f5e9aab42,
7586a7c0ba2f16ee6fe7f1ad95313775717e9f53,
  c8a1b14f43bb89a62c1471ec2931f152b37b3782,
50d33b98b1e23d1cd8743b3cac7a0ae5718b8b00]

CVE-2023-47233: Use after Free bug in brcmf_cfg80211_detach

stable 4.19, 5.10, and 5.4 were fixed.

Fixed status
cip/4.4: [726d91d1c97799544aee356136de385d11f81eab]
cip/4.4-st: [726d91d1c97799544aee356136de385d11f81eab]
mainline: [0f7352557a35ab7888bc7831411ec8a3cbe20d78]
stable/4.19: [202c503935042272e2f9e1bb549d5f69a8681169]
stable/5.10: [bacb8c3ab86dcd760c15903fcee58169bc3026aa]
stable/5.15: [8c36205123dc57349b59b4f1a2301eb278cbc731]
stable/5.4: [8e3f03f4ef7c36091f46e7349096efb5a2cdb3a1]
stable/6.1: [0b812f706fd7090be74812101114a0e165b36744]
stable/6.6: [190794848e2b9d15de92d502b6ac652806904f5a]
stable/6.7: [6678a1e7d896c00030b31491690e8ddc9a90767a]
stable/6.8: [0a7591e14a8da794d0b93b5d1c6254ccb23adacb]

CVE-2023-52458: block: add check that partition length needs to be
aligned with block size

stable 5.10 was fixed.

Fixed status
mainline: [6f64f866aa1ae6975c95d805ed51d7e9433a0016]
stable/5.10: [8f6dfa1f1efe6dcca2d43e575491d8fcbe922f62]
stable/5.15: [5010c27120962c85d2f421d2cf211791c9603503]
stable/6.1: [ef31cc87794731ffcb578a195a2c47d744e25fb8]
stable/6.6: [cb16cc1abda18a9514106d2ac8c8d7abc0be5ed8]
stable/6.7: [bcdc288e7bc008daf38ef0401b53e4a8bb61bbe5]

CVE-2023-52620: netfilter: nf_tables: disallow timeout for anonymous sets

stable 4.19, 5.10, and 5.4 were fixed.

Fixed status
mainline: [e26d3009efda338f19016df4175f354a9bd0a4ab]
stable/4.19: [116b0e8e4673a5faa8a739a19b467010c4d3058c]
stable/5.10: [6f3ae02bbb62f151b19162d5fdc9fe3d48450323]
stable/5.15: [00b19ee0dcc1aef06294471ab489bae26d94524e]
stable/5.4: [49ce99ae43314d887153e07cec8bb6a647a19268]
stable/6.1: [b7be6c737a179a76901c872f6b4c1d00552d9a1b]

CVE-2024-24857: Integer overflow bug was found in bluetooth device driver

stable 4.19, 5.10, and 5.4 were fixed.

Fixed status
mainline: [7835fcfd132eb88b87e8eb901f88436f63ab60f7]
stable/4.19: [466488b14a87dc97d8a3bf5e65a30bff032847c1]
stable/5.10: [e47088075477ea4129f9b000309f189e1392f138]
stable/5.15: [a8170af8b10e904c0052aa4ec31c653635730d92]
stable/5.4: [f5450973ebe8b7f6f66cfeafbb917671bb2477eb]
stable/6.1: [18e189442a5896255e764f8e875c13d16248ef2f]
stable/6.6: [d75632d0db3cdc31873d25756066a7f56bc87737]
stable/6.8: [d0bfebd8ca411697248d0cebe4ad2649f23ab0bf]

CVE-2024-24858: Race condition bug in bluetooth driver causes DoS

stable 4.19, 5.10, and 5.4 were fixed.

Fixed status
mainline: [7835fcfd132eb88b87e8eb901f88436f63ab60f7]
stable/4.19: [466488b14a87dc97d8a3bf5e65a30bff032847c1]
stable/5.10: [e47088075477ea4129f9b000309f189e1392f138]
stable/5.15: [a8170af8b10e904c0052aa4ec31c653635730d92]
stable/5.4: [f5450973ebe8b7f6f66cfeafbb917671bb2477eb]
stable/6.1: [18e189442a5896255e764f8e875c13d16248ef2f]
stable/6.6: [d75632d0db3cdc31873d25756066a7f56bc87737]
stable/6.8: [d0bfebd8ca411697248d0cebe4ad2649f23ab0bf]

CVE-2024-24859: Race condition bug in sniff_{min,max}_interval_set()
in bluetooth driver causes DoS

stable 4.19, 5.10, and 5.4 were fixed.

Fixed status
mainline: [7835fcfd132eb88b87e8eb901f88436f63ab60f7]
stable/4.19: [466488b14a87dc97d8a3bf5e65a30bff032847c1]
stable/5.10: [e47088075477ea4129f9b000309f189e1392f138]
stable/5.15: [a8170af8b10e904c0052aa4ec31c653635730d92]
stable/5.4: [f5450973ebe8b7f6f66cfeafbb917671bb2477eb]
stable/6.1: [18e189442a5896255e764f8e875c13d16248ef2f]
stable/6.6: [d75632d0db3cdc31873d25756066a7f56bc87737]
stable/6.8: [d0bfebd8ca411697248d0cebe4ad2649f23ab0bf]

CVE-2024-24861: Race condition bug was found in media/xc4000 device
driver in xc4000 xc4000_get_frequency()

stable 4.19, 5.10, and 5.4 were fixed.

Fixed status
cip/4.4: [7d5d34bfcf30298581bba6d5ca6cca69be117032]
cip/4.4-st: [7d5d34bfcf30298581bba6d5ca6cca69be117032]
mainline: [36d503ad547d1c75758a6fcdbec2806f1b6aeb41]
stable/4.19: [72ddb259a4d09f8e0d06cb2abc9a3eedfcb4200e]
stable/5.10: [7936e5c8da5bc975dec7e1e31e05da154f140cf6]
stable/5.15: [fec51819607ff0a80ad8ce678120fda80ca0b2fa]
stable/5.4: [ce6e52caded1d70e3a203da36a857b7d874e863f]
stable/6.1: [09c1be4d581d3356159abcc5a8a7a6c5f1bf1e77]
stable/6.6: [dc5e4f240473b64f7b2f24424e96c92435ebd8d7]
stable/6.7: [b0864de231dece0f7226b909521bebc86105743a]
stable/6.8: [5c26122885cedcb99606cdc06a3419db7feb1e1e]

CVE-2024-25739: ubi: Check for too small LEB size in VTBL code

stable 4.19, 5.10, and 5.4 were fixed.

Fixed status
cip/4.4: [42cee143e393919d1e983ac044efb8b0a6838bf0]
cip/4.4-st: [42cee143e393919d1e983ac044efb8b0a6838bf0]
mainline: [68a24aba7c593eafa8fd00f2f76407b9b32b47a9]
stable/4.19: [ff818a59ecdfb13a8eb4a38a87b869090dd1745c]
stable/5.10: [0a16a633a208b0b249bfaea5be699c07f304aaf0]
stable/5.15: [8ce982285414b741e2dd6ebb5a62e79dede44f7f]
stable/5.4: [4e09d5210ba481dd04ccc6e7d1b3b019d8bc3ddc]
stable/6.1: [5ecbc7465f66bb7eb2be2cd423f84000872e3560]
stable/6.6: [d1b505c988b711673d6a2de35222028be081d0d1]
stable/6.8: [04c4f2394970fa640bc794d627fe6b9406285406]

CVE-2024-26642: netfilter: nf_tables: disallow anonymous set with timeout flag

stable 4.19, 5.10, and 5.4 were fixed.

Fixed status
cip/4.4: [170bf61cffad04fa5e31f82702296fc8a6c561a2]
cip/4.4-st: [170bf61cffad04fa5e31f82702296fc8a6c561a2]
mainline: [16603605b667b70da974bea8216c93e7db043bf1]
stable/4.19: [e4988d8415bd0294d6f9f4a1e7095f8b50a97ca9]
stable/5.10: [fe40ffbca19dc70d7c6b1e3c77b9ccb404c57351]
stable/5.15: [7cdc1be24cc1bcd56a3e89ac4aef20e31ad09199]
stable/5.4: [e9a0d3f376eb356d54ffce36e7cc37514cbfbd6f]
stable/6.1: [72c1efe3f247a581667b7d368fff3bd9a03cd57a]
stable/6.6: [c0c2176d1814b92ea4c8e7eb7c9cd94cd99c1b12]
stable/6.7: [8e07c16695583a66e81f67ce4c46e94dece47ba7]

CVE-2024-26643: netfilter: nf_tables: mark set as dead when unbinding
anonymous set with timeout

stable 5.10 and 5.4 was fixed.

Fixed status
mainline: [552705a3650bbf46a22b1adedc1b04181490fc36]
stable/5.10: [e2d45f467096e931044f0ab7634499879d851a5c]
stable/5.15: [291cca35818bd52a407bc37ab45a15816039e363]
stable/5.4: [edcf1a3f182ecf8b6b805f0ce90570ea98c5f6bf]
stable/6.1: [406b0241d0eb598a0b330ab20ae325537d8d8163]
stable/6.6: [b2d6f9a5b1cf968f1eaa71085ceeb09c2cb276b1]
stable/6.7: [5224afbc30c3ca9ba23e752f0f138729b2c48dd8]

CVE-2024-26654: ALSA: sh: aica: reorder cleanup operations to avoid UAF bugs

stable 4.19, 5.10, and 5.4 were fixed.

Fixed status
mainline: [051e0840ffa8ab25554d6b14b62c9ab9e4901457]
stable/4.19: [eeb2a2ca0b8de7e1c66afaf719529154e7dc60b2]
stable/5.10: [aa39e6878f61f50892ee2dd9d2176f72020be845]
stable/5.15: [8c990221681688da34295d6d76cc2f5b963e83f5]
stable/5.4: [4206ad65a0ee76920041a755bd3c17c6ba59bba2]
stable/6.1: [9d66ae0e7bb78b54e1e0525456c6b54e1d132046]
stable/6.6: [61d4787692c1fccdc268ffa7a891f9c149f50901]
stable/6.7: [e955e8a7f38a856fc6534ba4e6bffd4d5cc80ac3]
stable/6.8: [3c907bf56905de7d27b329afaf59c2fb35d17b04]

CVE-2024-26687: xen/events: close evtchn after mapping cleanup

stable 5.10 and 5.4 were fixed.

Fixed status
mainline: [fa765c4b4aed2d64266b694520ecb025c862c5a9]
stable/5.10: [0fc88aeb2e32b76db3fe6a624b8333dbe621b8fd]
stable/5.15: [ea592baf9e41779fe9a0424c03dd2f324feca3b3]
stable/5.4: [9470f5b2503cae994098dea9682aee15b313fa44]
stable/6.1: [585a344af6bcac222608a158fc2830ff02712af5]
stable/6.6: [20980195ec8d2e41653800c45c8c367fa1b1f2b4]
stable/6.7: [9be71aa12afa91dfe457b3fb4a444c42b1ee036b]

CVE-2024-26810: vfio/pci: Lock external INTx masking ops

stable 5.10 and 5.4 were fixed.

Fixed status
mainline: [810cd4bb53456d0503cc4e7934e063835152c1b7]
stable/5.10: [3dd9be6cb55e0f47544e7cdda486413f7134e3b3]
stable/5.15: [ec73e079729258a05452356cf6d098bf1504d5a6]
stable/5.4: [1e71b6449d55179170efc8dee8664510bb813b42]
stable/6.1: [3fe0ac10bd117df847c93408a9d428a453cd60e5]
stable/6.6: [04a4a017b9ffd7b0f427b8c376688d14cb614651]
stable/6.8: [03505e3344b0576fd619416793a31eae9c5b73bf]

CVE-2024-26812: vfio/pci: Create persistent INTx handler

stable 5.10 and 5.4 were fixed.

Fixed status
mainline: [18c198c96a815c962adc2b9b77909eec0be7df4d]
stable/5.10: [27d40bf72dd9a6600b76ad05859176ea9a1b4897]
stable/5.15: [4cb0d7532126d23145329826c38054b4e9a05e7c]
stable/5.4: [b18fa894d615c8527e15d96b76c7448800e13899]
stable/6.1: [7d29d4c72c1e196cce6969c98072a272d1a703b3]
stable/6.6: [69276a555c740acfbff13fb5769ee9c92e1c828e]
stable/6.8: [0e09cf81959d9f12b75ad5c6dd53d237432ed034]

CVE-2024-26813: vfio/platform: Create persistent IRQ handlers

stable 5.10 and 5.4 were fixed.

Fixed status
mainline: [675daf435e9f8e5a5eab140a9864dfad6668b375]
stable/5.10: [09452c8fcbd7817c06e8e3212d99b45917e603a5]
stable/5.15: [cc5838f19d39a5fef04c468199699d2a4578be3a]
stable/5.4: [07afdfd8a68f9eea8db0ddc4626c874f29d2ac5e]
stable/6.1: [7932db06c82c5b2f42a4d1a849d97dba9ce4a362]
stable/6.6: [62d4e43a569b67929eb3319780be5359694c8086]
stable/6.8: [0f8d8f9c2173a541812dd750529f4a415117eb29]

CVE-2024-26814: vfio/fsl-mc: Block calling interrupt handler without trigger

stable 5.10 was fixed.

Fixed status
mainline: [7447d911af699a15f8d050dfcb7c680a86f87012]
stable/5.10: [a563fc18583ca4f42e2fdd0c70c7c618288e7ede]
stable/5.15: [250219c6a556f8c69c5910fca05a59037e24147d]
stable/6.1: [083e750c9f5f4c3bf61161330fb84d7c8e8bb417]
stable/6.6: [ee0bd4ad780dfbb60355b99f25063357ab488267]
stable/6.8: [6ec0d88166dac43f29e96801c0927d514f17add9]

CVE-2024-27437: vfio/pci: Disable auto-enable of exclusive INTx IRQ

stable 5.10 and 5.4 were fixed.

Fixed status
mainline: [fe9a7082684eb059b925c535682e68c34d487d43]
stable/5.10: [561d5e1998d58b54ce2bbbb3e843b669aa0b3db5]
stable/5.15: [b7a2f0955ffceffadfe098b40b50307431f45438]
stable/5.4: [26389925d6c2126fb777821a0a983adca7ee6351]
stable/6.1: [139dfcc4d723ab13469881200c7d80f49d776060]
stable/6.6: [2a4a666c45107206605b7b5bc20545f8aabc4fa2]
stable/6.8: [bf0bc84a20e6109ab07d5dc072067bd01eb931ec]

Currently tracking CVEs

CVE-2021-31615: Unencrypted Bluetooth Low Energy baseband links in
Bluetooth Core Specifications 4.0 through 5.2

There is no fix information.

CVE-2020-26556: kernel: malleable commitment Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26557: kernel: predictable Authvalue in Bluetooth Mesh
Provisioning Leads to MITM

No fix information.

CVE-2020-26559: kernel: Authvalue leak in Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26560: kernel: impersonation attack in Bluetooth Mesh Provisioning

No fix information.

Regards,
-- 
Masami Ichikawa
Cybertrust Japan Co., Ltd.

Email :masami.ichikawa@cybertrust.co.jp
          :masami.ichikawa@miraclelinux.com


^ permalink raw reply	[flat|nested] 33+ messages in thread

* [kernel-cve-report] New CVE entries this week
@ 2024-04-11  2:21 Masami Ichikawa
  0 siblings, 0 replies; 33+ messages in thread
From: Masami Ichikawa @ 2024-04-11  2:21 UTC (permalink / raw)
  To: cip-dev

Hi!

It's this week's CVE report.

This week reported 82 new CVEs and 16 updated CVEs.

* New CVEs

CVE-2024-26745: powerpc/pseries/iommu: IOMMU table is not initialized
for kdump over SR-IOV

Announce: https://lore.kernel.org/linux-cve-announce/2024040454-CVE-2024-26745-fa88@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit b1fc44e ("pseries/iommu/ddw: Fix kdump to work in
absence of ibm,dma-window") in v6.0-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc7.

Fixed status
mainline: [09a3c1e46142199adcee372a420b024b4fc61051]
stable/6.1: [7eb95e0af5c9c2e6fad50356eaf32d216d0e7bc3]
stable/6.6: [d4d1e4b1513d975961de7bb4f75e450a92d65ebf]
stable/6.7: [5da6d306f315344af1ca2eff4bd9b10b130f0c28]

CVE-2024-26746: dmaengine: idxd: Ensure safe user copy of completion record

Announce: https://lore.kernel.org/linux-cve-announce/2024040457-CVE-2024-26746-8aa9@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit c2f156b ("dmaengine: idxd: create kmem cache for
event log fault items") in v6.4-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc7.

Fixed status
mainline: [d3ea125df37dc37972d581b74a5d3785c3f283ab]
stable/6.6: [5e3022ea42e490a36ec6f2cfa6fc603deb0bace4]
stable/6.7: [bb71e040323175e18c233a9afef32ba14fa64eb7]

CVE-2024-26750: af_unix: Drop oob_skb ref before purging queue in GC.

Announce: https://lore.kernel.org/linux-cve-announce/2024040457-CVE-2024-26750-4468@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 25236c91b ("af_unix: Fix task hung while purging
oob_skb in GC.") in 6.8-rc5.
This commit was backported to 5.15, 6.1, 6.6, and 6.7.
Fixed in 6.8-rc6.

Fixed status
mainline: [aa82ac51d63328714645c827775d64dbfd9941f3]
stable/5.15: [6c480d0f131862645d172ca9e25dc152b1a5c3a6]
stable/6.1: [c4c795b21dd23d9514ae1c6646c3fb2c78b5be60]
stable/6.6: [e9eac260369d0cf57ea53df95427125725507a0d]
stable/6.7: [43ba9e331559a30000c862eea313248707afa787]

CVE-2024-26780: af_unix: Fix task hung while purging oob_skb in GC.

Announce: https://lore.kernel.org/linux-cve-announce/2024040458-CVE-2024-26780-9951@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 1279f9d ("af_unix: Call kfree_skb() for dead
unix_(sk)->oob_skb in GC.") in 6.8-rc4.
This commit was backported to 5.15, 6.1, 6.6, and 6.7.
Fixed in 6.8-rc5.

Fixed status
mainline: [25236c91b5ab4a26a56ba2e79b8060cf4e047839]
stable/5.15: [36f7371de977f805750748e80279be7e370df85c]
stable/6.1: [2a3d40b4025fcfe51b04924979f1653993b17669]
stable/6.6: [69e0f04460f4037e01e29f0d9675544f62aafca3]
stable/6.7: [cb8890318dde26fc89c6ea67d6e9070ab50b6e91]

CVE-2024-26781: mptcp: fix possible deadlock in subflow diag

Announce: https://lore.kernel.org/linux-cve-announce/2024040458-CVE-2024-26781-0389@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit b8adb69 ("mptcp: fix lockless access in subflow
ULP diag") in 6.8-rc6.
This commit was backported to 5.10, 5.15, 6.1, 6.6, and 6.7.
Fixed in 6.8-rc7.

Fixed status
mainline: [d6a9608af9a75d13243d217f6ce1e30e57d56ffe]
stable/5.10: [70e5b013538d5e4cb421afed431a5fcd2a5d49ee]
stable/5.15: [cc32ba2fdf3f8b136619fff551f166ba51ec856d]
stable/6.1: [f27d319df055629480b84b9288a502337b6f2a2e]
stable/6.6: [fa8c776f4c323a9fbc8ddf25edcb962083391430]
stable/6.7: [d487e7ba1bc7444d5f062c4930ef8436c47c7e63]

CVE-2024-26782: mptcp: fix double-free on socket dismantle

Announce: https://lore.kernel.org/linux-cve-announce/2024040458-CVE-2024-26782-71ca@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit cf7da0d ("mptcp: Create SUBFLOW socket for
incoming connections") in v5.6-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc7.

Fixed status
mainline: [10048689def7e40a4405acda16fdc6477d4ecc5c]
stable/5.10: [f74362a004225df935863dea6eb7d82daaa5b16e]
stable/5.15: [4a4eeb6912538c2d0b158e8d11b62d96c1dada4e]
stable/6.1: [d93fd40c62397326046902a2c5cb75af50882a85]
stable/6.6: [ce0809ada38dca8d6d41bb57ab40494855c30582]
stable/6.7: [85933e80d077c9ae2227226beb86c22f464059cc]

CVE-2024-26783: mm/vmscan: fix a bug calling wakeup_kswapd() with a
wrong zone index

Announce: https://lore.kernel.org/linux-cve-announce/2024040458-CVE-2024-26783-68c8@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit c574bbe ("NUMA balancing: optimize page placement
for memory tiering system") in v5.18-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc7.

Fixed status
mainline: [2774f256e7c0219e2b0a0894af1c76bdabc4f974]
stable/6.6: [d6159bd4c00594249e305bfe02304c67c506264e]
stable/6.7: [bdd21eed8b72f9e28d6c279f6db258e090c79080]

CVE-2024-26784: pmdomain: arm: Fix NULL dereference on scmi_perf_domain removal

Announce: https://lore.kernel.org/linux-cve-announce/2024040459-CVE-2024-26784-9e9c@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 2af23ce ("pmdomain: arm: Add the SCMI performance
domain") in v6.7-rc1.
This commit is not backported to older stable kernel.
Fixed in v6.8-rc7.

Fixed status
mainline: [eb5555d422d0fc325e1574a7353d3c616f82d8b5]
stable/6.7: [f6aaf131e4d4a9a26040ecc018eb70ab8b3d355d]

CVE-2024-26785: iommufd: Fix protection fault in iommufd_test_syz_conv_iova

Announce: https://lore.kernel.org/linux-cve-announce/2024040459-CVE-2024-26785-857d@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 9227da7 ("iommufd: Add
iommufd_access_change_ioas(_id) helpers") in v6.6-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc7.

Fixed status
mainline: [cf7c2789822db8b5efa34f5ebcf1621bc0008d48]
stable/6.7: [fc719ecbca45c9c046640d72baddba3d83e0bc0b]

CVE-2024-26786: iommufd: Fix iopt_access_list_id overwrite bug

Announce: https://lore.kernel.org/linux-cve-announce/2024040459-CVE-2024-26786-802f@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 9227da7 ("iommufd: Add
iommufd_access_change_ioas(_id) helpers") in v6.6-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc7.

Fixed status
mainline: [aeb004c0cd6958e910123a1607634401009c9539]
stable/6.6: [f1fb745ee0a6fe43f1d84ec369c7e6af2310fda9]
stable/6.7: [9526a46cc0c378d381560279bea9aa34c84298a0]

CVE-2024-26787: mmc: mmci: stm32: fix DMA API overlapping mappings warning

Announce: https://lore.kernel.org/linux-cve-announce/2024040459-CVE-2024-26787-48c0@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 46b723d ("mmc: mmci: add stm32 sdmmc variant") in
v4.20-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc7.

Fixed status
mainline: [6b1ba3f9040be5efc4396d86c9752cdc564730be]
stable/5.10: [0224cbc53ba82b84affa7619b6d1b1a254bc2c53]
stable/5.15: [5ae5060e17a3fc38e54c3e5bd8abd6b1d5bfae7c]
stable/6.1: [70af82bb9c897faa25a44e4181f36c60312b71ef]
stable/6.6: [176e66269f0de327375fc0ea51c12c2f5a97e4c4]
stable/6.7: [d610a307225951929b9dff807788439454476f85]

CVE-2024-26788: dmaengine: fsl-qdma: init irq after reg initialization

Announce: https://lore.kernel.org/linux-cve-announce/2024040400-CVE-2024-26788-1f84@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit b092529 ("dmaengine: fsl-qdma: Add qDMA
controller driver for Layerscape SoCs") in v5.1-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc7.

Fixed status
mainline: [87a39071e0b639f45e05d296cc0538eef44ec0bd]
stable/5.10: [9579a21e99fe8dab22a253050ddff28d340d74e1]
stable/5.15: [4529c084a320be78ff2c5e64297ae998c6fdf66b]
stable/5.4: [3cc5fb824c2125aa3740d905b3e5b378c8a09478]
stable/6.1: [474d521da890b3e3585335fb80a6044cb2553d99]
stable/6.6: [a69c8bbb946936ac4eb6a6ae1e849435aa8d947d]
stable/6.7: [677102a930643c31f1b4c512b041407058bdfef8]

CVE-2024-26789: crypto: arm64/neonbs - fix out-of-bounds access on short input

Announce: https://lore.kernel.org/linux-cve-announce/2024040400-CVE-2024-26789-1744@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit fc074e1 ("crypto: arm64/aes-neonbs-ctr - fallback
to plain NEON for final chunk") in v5.18-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc7.

Fixed status
mainline: [1c0cf6d19690141002889d72622b90fc01562ce4]
stable/6.1: [034e2d70b5c7f578200ad09955aeb2aa65d1164a]
stable/6.6: [1291d278b5574819a7266568ce4c28bce9438705]
stable/6.7: [9e8ecd4908b53941ab6f0f51584ab80c6c6606c4]

CVE-2024-26790: dmaengine: fsl-qdma: fix SoC may hang on 16 byte unaligned read

Announce: https://lore.kernel.org/linux-cve-announce/2024040400-CVE-2024-26790-a4a4@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit b092529 ("dmaengine: fsl-qdma: Add qDMA
controller driver for Layerscape SoCs") in v5.1-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc7.

Fixed status
mainline: [9d739bccf261dd93ec1babf82f5c5d71dd4caa3e]
stable/5.10: [bb3a06e9b9a30e33d96aadc0e077be095a4f8580]
stable/5.15: [106c1ac953a66556ec77456c46e818208d3a9bce]
stable/5.4: [518d78b4fac68cac29a263554d7f3b19da99d0da]
stable/6.1: [237ecf1afe6c22534fa43abdf2bf0b0f52de0aaa]
stable/6.6: [5b696e9c388251f1c7373be92293769a489fd367]
stable/6.7: [ad2f8920c314e0a2d9e984fc94b729eca3cda471]

CVE-2024-26791: btrfs: dev-replace: properly validate device names

Announce: https://lore.kernel.org/linux-cve-announce/2024040400-CVE-2024-26791-1002@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc7.
Linux 4.4 may be affected. Vulnerable function would be
btrfs_dev_replace_start() in fs/btrfs/dev-replace.c.
(https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/tree/fs/btrfs/dev-replace.c?h=linux-4.4.y-st#n308)

Fixed status
mainline: [9845664b9ee47ce7ee7ea93caf47d39a9d4552c4]
stable/4.19: [11d7a2e429c02d51e2dc90713823ea8b8d3d3a84]
stable/5.10: [2886fe308a83968dde252302884a1e63351cf16d]
stable/5.15: [ab2d68655d0f04650bef09fee948ff80597c5fb9]
stable/5.4: [c6652e20d7d783d060fe5f987eac7b5cabe31311]
stable/6.1: [f590040ce2b712177306b03c2a63b16f7d48d3c8]
stable/6.6: [b1690ced4d2d8b28868811fb81cd33eee5aefee1]
stable/6.7: [343eecb4ff49a7b1cc1dfe86958a805cf2341cfb]

CVE-2024-26792: btrfs: fix double free of anonymous device after
snapshot creation failure

Announce: https://lore.kernel.org/linux-cve-announce/2024040401-CVE-2024-26792-6048@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit e03ee2f ("btrfs: do not ASSERT() if the newly
created subvolume already got read") in 6.8-rc4.
This commit was backported to 5.10, 5.15, 6.1, 6.6, and 6.7.
Fixed in 6.8-rc7.

Fixed status
mainline: [e2b54eaf28df0c978626c9736b94f003b523b451]
stable/6.1: [c34adc20b91a8e55e048b18d63f4f4ae003ecf8f]
stable/6.6: [eb3441093aad251418921246fc3b224fd1575701]
stable/6.7: [c8ab7521665bd0f8bc4a900244d1d5a7095cc3b9]

CVE-2024-26793: gtp: fix use-after-free and null-ptr-deref in gtp_newlink()

Announce: https://lore.kernel.org/linux-cve-announce/2024040401-CVE-2024-26793-2beb@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 459aa66 ("gtp: add initial driver for datapath of
GPRS Tunneling Protocol (GTP-U)") in v4.7-rc1.
Linux 4.4 is not affected.
Fixed in v6.8-rc7.

Fixed status
mainline: [616d82c3cfa2a2146dd7e3ae47bda7e877ee549e]
stable/4.19: [01129059d5141d62fae692f7a336ae3bc712d3eb]
stable/5.10: [e668b92a3a01429923fd5ca13e99642aab47de69]
stable/5.15: [9376d059a705c5dfaac566c2d09891242013ae16]
stable/5.4: [ec92aa2cab6f0048f10d6aa4f025c5885cb1a1b6]
stable/6.1: [abd32d7f5c0294c1b2454c5a3b13b18446bac627]
stable/6.6: [93dd420bc41531c9a31498b9538ca83ba6ec191e]
stable/6.7: [5366969a19a8a0d2ffb3d27ef6e8905e5e4216f8]

CVE-2024-26794: btrfs: fix race between ordered extent completion and fiemap

Announce:
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit b0ad381 ("btrfs: fix deadlock with fiemap and
extent locking") in 6.8-rc6.
This commit was backported to 6.6 and 6.7.
Fixed in 6.8-rc7.

Fixed status
mainline: [a1a4a9ca77f143c00fce69c1239887ff8b813bec]
stable/6.6: [d43f8e58f10a44df8c08e7f7076f3288352cd168]
stable/6.7: [31d07a757c6d3430e03cc22799921569999b9a12]

CVE-2024-26795: riscv: Sparse-Memory/vmemmap out-of-bounds fix

Announce: https://lore.kernel.org/linux-cve-announce/2024040402-CVE-2024-26795-404a@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit d95f1a5 ("RISC-V: Implement sparsemem") in v5.4-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc7.

Fixed status
mainline: [a11dd49dcb9376776193e15641f84fcc1e5980c9]
stable/5.10: [8af1c121b0102041809bc137ec600d1865eaeedd]
stable/5.15: [5941a90c55d3bfba732b32208d58d997600b44ef]
stable/6.1: [8310080799b40fd9f2a8b808c657269678c149af]
stable/6.6: [a278d5c60f21aa15d540abb2f2da6e6d795c3e6e]
stable/6.7: [2a1728c15ec4f45ed9248ae22f626541c179bfbe]

CVE-2024-26796: drivers: perf: ctr_get_width function for legacy is not defined

Announce: https://lore.kernel.org/linux-cve-announce/2024040402-CVE-2024-26796-85c5@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit cc4c07c ("drivers: perf: Implement perf event
mmap support  in the SBI backend") in v6.6-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc7.

Fixed status
mainline: [682dc133f83e0194796e6ea72eb642df1c03dfbe]
stable/6.6: [e0d17ee872cf8d0f51cc561329b8e1a0aa792bbb]
stable/6.7: [e4f50e85de5a6b21dfdc0d7ca435eba4f62935c3]

CVE-2024-26797: drm/amd/display: Prevent potential buffer overflow in
map_hw_resources

Announce: https://lore.kernel.org/linux-cve-announce/2024040402-CVE-2024-26797-704f@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 7966f31 ("drm/amd/display: Introduce DML2") in v6.7-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc7.

Fixed status
mainline: [0f8ca019544a252d1afb468ce840c6dcbac73af4]
stable/6.7: [50a6302cf881f67f1410461a68fe9eabd00ff31d]

CVE-2024-26798: fbcon: always restore the old font data in fbcon_do_set_font()

Announce: https://lore.kernel.org/linux-cve-announce/2024040402-CVE-2024-26798-191e@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit a5a9230 ("fbdev: fbcon: Properly revert changes
when vc_resize() failed") in v6.0-rc3.
This commit was backported to 5.15.
Fixed in v6.8-rc7.

Fixed status
mainline: [00d6a284fcf3fad1b7e1b5bc3cd87cbfb60ce03f]
stable/5.15: [20a4b5214f7bee13c897477168c77bbf79683c3d]
stable/6.1: [2f91a96b892fab2f2543b4a55740c5bee36b1a6b]
stable/6.6: [73a6bd68a1342f3a44cac9dffad81ad6a003e520]
stable/6.7: [a2c881413dcc5d801bdc9535e51270cc88cb9cd8]

CVE-2024-26799: ASoC: qcom: Fix uninitialized pointer dmactl

Announce: https://lore.kernel.org/linux-cve-announce/2024040403-CVE-2024-26799-1fd6@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit b81af58 ("ASoC: qcom: Add lpass CPU driver for
codec dma control") in v5.18-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc7.

Fixed status
mainline: [1382d8b55129875b2e07c4d2a7ebc790183769ee]
stable/6.6: [99adc8b4d2f38bf0d06483ec845bc48f60c3f8cf]
stable/6.7: [d5a7726e6ea62d447b79ab5baeb537ea6bdb225b]

CVE-2024-26800: tls: fix use-after-free on failed backlog decryption

Announce: https://lore.kernel.org/linux-cve-announce/2024040403-CVE-2024-26800-0bf4@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 8590541 ("net: tls: handle backlogging of crypto
requests") in 6.8-rc5.
This commit was backported to 6.1, 6.6, and 6.7.
Fixed in 6.8-rc7.

Fixed status
mainline: [13114dc5543069f7b97991e3b79937b6da05f5b0]
stable/6.1: [f2b85a4cc763841843de693bbd7308fe9a2c4c89]
stable/6.6: [81be85353b0f5a7b660635634b655329b429eefe]
stable/6.7: [1ac9fb84bc7ecd4bc6428118301d9d864d2a58d1]

CVE-2024-26801: Bluetooth: Avoid potential use-after-free in hci_error_reset

Announce: https://lore.kernel.org/linux-cve-announce/2024040403-CVE-2024-26801-da9f@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit c7741d1 ("Bluetooth: Perform a power cycle when
receiving hardware error event") in v4.0-rc1.
Fixed in v6.8-rc7.

Fixed status
mainline: [2449007d3f73b2842c9734f45f0aadb522daf592]
stable/4.19: [e0b278650f07acf2e0932149183458468a731c03]
stable/5.10: [6dd0a9dfa99f8990a08eb8fdd8e79bee31c7d8e2]
stable/5.15: [da4569d450b193e39e87119fd316c0291b585d14]
stable/5.4: [98fb98fd37e42fd4ce13ff657ea64503e24b6090]
stable/6.1: [45085686b9559bfbe3a4f41d3d695a520668f5e1]
stable/6.6: [2ab9a19d896f5a0dd386e1f001c5309bc35f433b]
stable/6.7: [dd594cdc24f2e48dab441732e6dfcafd6b0711d1]

CVE-2024-26802: stmmac: Clear variable when destroying workqueue

Announce: https://lore.kernel.org/linux-cve-announce/2024040403-CVE-2024-26802-b3da@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 5a55861 ("net: stmmac: support FPE link partner
hand-shaking procedure") in v5.13-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc7.

Fixed status
mainline: [8af411bbba1f457c33734795f024d0ef26d0963f]
stable/5.15: [8e99556301172465c8fe33c7f78c39a3d4ce8462]
stable/6.1: [17ccd9798fe0beda3db212cfa3ebe373f605cbd6]
stable/6.6: [699b103e48ce32d03fc86c35b37ee8ae4288c7e3]
stable/6.7: [f72cf22dccc94038cbbaa1029cb575bf52e5cbc8]

CVE-2024-26803: net: veth: clear GRO when clearing XDP even when down

Announce: https://lore.kernel.org/linux-cve-announce/2024040404-CVE-2024-26803-9985@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit d3256ef ("veth: allow enabling NAPI even without
XDP") in v5.13-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc7.

Fixed status
mainline: [fe9f801355f0b47668419f30f1fac1cf4539e736]
stable/5.15: [f011c103e654d83dc85f057a7d1bd0960d02831c]
stable/6.1: [7985d73961bbb4e726c1be7b9cd26becc7be8325]
stable/6.6: [16edf51f33f52dff70ed455bc40a6cc443c04664]
stable/6.7: [8f7a3894e58e6f5d5815533cfde60e3838947941]

CVE-2024-26804: net: ip_tunnel: prevent perpetual headroom growth

Announce: https://lore.kernel.org/linux-cve-announce/2024040404-CVE-2024-26804-a6ff@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 243aad8 ("ip_gre: include route header_len in
max_headroom calculation") in v2.6.34-rc3.
Fixed in v6.8-rc7.

Fixed status
mainline: [5ae1e9922bbdbaeb9cfbe91085ab75927488ac0f]
stable/5.10: [2e95350fe9db9d53c701075060ac8ac883b68aee]
stable/5.15: [afec0c5cd2ed71ca95a8b36a5e6d03333bf34282]
stable/5.4: [f81e94d2dcd2397137edcb8b85f4c5bed5d22383]
stable/6.1: [ab63de24ebea36fe73ac7121738595d704b66d96]
stable/6.6: [a0a1db40b23e8ff86dea2786c5ea1470bb23ecb9]
stable/6.7: [049d7989c67e8dd50f07a2096dbafdb41331fb9b]

CVE-2024-26805: netlink: Fix kernel-infoleak-after-free in __skb_datagram_iter

Announce: https://lore.kernel.org/linux-cve-announce/2024040404-CVE-2024-26805-7016@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 1853c94 ("netlink, mmap: transform mmap skb into
full skb on taps") in v4.3-rc3.
Fixed in v6.8-rc7.

Fixed status
mainline: [661779e1fcafe1b74b3f3fe8e980c1e207fea1fd]
stable/4.19: [ec343a55b687a452f5e87f3b52bf9f155864df65]
stable/5.10: [f19d1f98e60e68b11fc60839105dd02a30ec0d77]
stable/5.15: [c71ed29d15b1a1ed6c464f8c3536996963046285]
stable/5.4: [9ae51361da43270f4ba0eb924427a07e87e48777]
stable/6.1: [0b27bf4c494d61e5663baa34c3edd7ccebf0ea44]
stable/6.6: [d3ada42e534a83b618bbc1e490d23bf0fdae4736]
stable/6.7: [59fc3e3d049e39e7d0d271f20dd5fb47c57faf1d]

CVE-2024-26806: spi: cadence-qspi: remove system-wide suspend helper
calls from runtime PM hooks

Announce: https://lore.kernel.org/linux-cve-announce/2024040404-CVE-2024-26806-4644@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 0578a6d ("spi: spi-cadence-quadspi: add runtime
pm support") in v6.7-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc7.

Fixed status
mainline: [959043afe53ae80633e810416cee6076da6e91c6]
stable/6.7: [041562ebc4759c9932b59a06527f8753b86da365]

CVE-2024-26807: spi: cadence-qspi: fix pointer reference in runtime PM hooks

Announce: https://lore.kernel.org/linux-cve-announce/2024040405-CVE-2024-26807-c071@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 2087e85 ("spi: cadence-quadspi: fix
suspend-resume implementations") in v6.4-rc1.
This commit is backported to 4.19, 5.10, 5.15, 5.4, and 6.1.
Fixed in v6.8-rc7.

Fixed status
mainline: [32ce3bb57b6b402de2aec1012511e7ac4e7449dc]
stable/6.6: [03f1573c9587029730ca68503f5062105b122f61]
stable/6.7: [34e1d5c4407c78de0e3473e1fbf8fb74dbe66d03]

CVE-2024-26808: netfilter: nft_chain_filter: handle NETDEV_UNREGISTER
for inet/ingress basechain

Announce: https://lore.kernel.org/linux-cve-announce/2024040458-CVE-2024-26808-2df2@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 60a3815 ("netfilter: add inet ingress support")
in v5.10-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc2.

Fixed status
mainline: [01acb2e8666a6529697141a6017edbf206921913]
stable/5.10: [9489e214ea8f2a90345516016aa51f2db3a8cc2f]
stable/5.15: [70f17b48c86622217a58d5099d29242fc9adac58]
stable/6.1: [af149a46890e8285d1618bd68b8d159bdb87fdb3]
stable/6.6: [e5888acbf1a3d8d021990ce6c6061fd5b2bb21b4]
stable/6.7: [36a0a80f32209238469deb481967d777a3d539ee]

CVE-2024-26809: netfilter: nft_set_pipapo: release elements in clone
only from destroy path

Announce: https://lore.kernel.org/linux-cve-announce/2024040401-CVE-2024-26809-b0d1@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 9827a0e ("netfilter: nft_set_pipapo: release
elements in clone from abort path") in v5.19-rc6.
This commit was backported to 5.10 and 5.15.
Fixed in v6.9-rc1.

Fixed status
mainline: [b0e256f3dd2ba6532f37c5c22e07cb07a36031ee]
stable/5.10: [b36b83297ff4910dfc8705402c8abffd4bbf8144]
stable/5.15: [362508506bf545e9ce18c72a2c48dcbfb891ab9c]
stable/6.1: [5ad233dc731ab64cdc47b84a5c1f78fff6c024af]
stable/6.6: [ff90050771412b91e928093ccd8736ae680063c2]
stable/6.7: [821e28d5b506e6a73ccc367ff792bd894050d48b]

CVE-2024-26810: vfio/pci: Lock external INTx masking ops

Announce: https://lore.kernel.org/linux-cve-announce/2024040548-CVE-2024-26810-4371@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 89e1f7d ("vfio: Add PCI device driver") in v3.6-rc1.
Fixed in v6.9-rc1.
Backporting the fix to 4.19 was failed.
https://lore.kernel.org/stable/20240327122702.2841569-1-sashal@kernel.org/
Patch for 5.4 and 5.10 is available.
https://lore.kernel.org/stable/20240401165302.3699643-1-alex.williamson@redhat.com/

Fixed status
mainline: [810cd4bb53456d0503cc4e7934e063835152c1b7]
stable/5.15: [ec73e079729258a05452356cf6d098bf1504d5a6]
stable/6.1: [3fe0ac10bd117df847c93408a9d428a453cd60e5]
stable/6.6: [04a4a017b9ffd7b0f427b8c376688d14cb614651]
stable/6.8: [03505e3344b0576fd619416793a31eae9c5b73bf]

CVE-2024-26812: vfio/pci: Create persistent INTx handler

Announce: https://lore.kernel.org/linux-cve-announce/2024040550-CVE-2024-26812-1e08@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 89e1f7d ("vfio: Add PCI device driver") in v3.6-rc1.
Fixed in v6.9-rc1.
Backporting the fix to 4.19 was failed.
https://lore.kernel.org/stable/20240327122755.2842328-1-sashal@kernel.org/
Patch for 5.4 and 5.10 is available.
https://lore.kernel.org/stable/20240401165302.3699643-1-alex.williamson@redhat.com/

Fixed status
mainline: [18c198c96a815c962adc2b9b77909eec0be7df4d]
stable/5.15: [4cb0d7532126d23145329826c38054b4e9a05e7c]
stable/6.1: [7d29d4c72c1e196cce6969c98072a272d1a703b3]
stable/6.6: [69276a555c740acfbff13fb5769ee9c92e1c828e]
stable/6.8: [0e09cf81959d9f12b75ad5c6dd53d237432ed034]

CVE-2024-26813: vfio/platform: Create persistent IRQ handlers

Announce: https://lore.kernel.org/linux-cve-announce/2024040551-CVE-2024-26813-b9e8@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 57f972e ("vfio/platform: trigger an interrupt via
eventfd") in v4.1-rc1.
Fixed in v6.9-rc1.
Backporting the fix to 4.19 was failed.
https://lore.kernel.org/stable/20240327122707.2841648-1-sashal@kernel.org/
Patch for 5.4 and 5.10 is available
https://lore.kernel.org/stable/20240401165302.3699643-6-alex.williamson@redhat.com/

Fixed status
mainline: [675daf435e9f8e5a5eab140a9864dfad6668b375]
stable/5.15: [cc5838f19d39a5fef04c468199699d2a4578be3a]
stable/6.1: [7932db06c82c5b2f42a4d1a849d97dba9ce4a362]
stable/6.6: [62d4e43a569b67929eb3319780be5359694c8086]
stable/6.8: [0f8d8f9c2173a541812dd750529f4a415117eb29]

CVE-2024-26814: vfio/fsl-mc: Block calling interrupt handler without trigger

Announce: https://lore.kernel.org/linux-cve-announce/2024040551-CVE-2024-26814-b578@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit cc0ee20 ("vfio/fsl-mc: trigger an interrupt via
eventfd") in v5.10-rc1.
Fixed in v6.9-rc1.
Patch for 5.4 and 5.10 is available
https://lore.kernel.org/stable/20240401165302.3699643-6-alex.williamson@redhat.com/

Fixed status
mainline: [7447d911af699a15f8d050dfcb7c680a86f87012]
stable/5.15: [b7a2f0955ffceffadfe098b40b50307431f45438]
stable/6.1: [083e750c9f5f4c3bf61161330fb84d7c8e8bb417]
stable/6.6: [ee0bd4ad780dfbb60355b99f25063357ab488267]
stable/6.8: [bf0bc84a20e6109ab07d5dc072067bd01eb931ec]

CVE-2024-27437: vfio/pci: Disable auto-enable of exclusive INTx IRQ

Announce: https://lore.kernel.org/linux-cve-announce/2024040551-CVE-2024-27437-cc07@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 89e1f7d ("vfio: Add PCI device driver") in v3.6-rc1.
Fixed in v6.9-rc1.
Backporting the fix to 4.19 was failed.
https://lore.kernel.org/stable/20240327122510.2840000-1-sashal@kernel.org/
Patch for 5.4 and 5.10 is available
https://lore.kernel.org/stable/20240401165302.3699643-6-alex.williamson@redhat.com/

Fixed status
mainline: [fe9a7082684eb059b925c535682e68c34d487d43]
stable/5.15: [b7a2f0955ffceffadfe098b40b50307431f45438]
stable/6.1: [139dfcc4d723ab13469881200c7d80f49d776060]
stable/6.6: [2a4a666c45107206605b7b5bc20545f8aabc4fa2]
stable/6.8: [bf0bc84a20e6109ab07d5dc072067bd01eb931ec]

CVE-2024-26811: ksmbd: validate payload size in ipc response

Announce: https://lore.kernel.org/linux-cve-announce/2024040822-CVE-2024-26811-f7f5@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.9-rc3.
The ksmbd was introduced in 5.15 so prior to Linux 5.15 is not affected.

Fixed status
mainline: [a677ebd8ca2f2632ccdecbad7b87641274e15aac]
stable/6.1: [51a6c2af9d20203ddeeaf73314ba8854b38d01bd]
stable/6.6: [a637fabac554270a851033f5ab402ecb90bc479c]
stable/6.8: [76af689a45aa44714b46d1a7de4ffdf851ded896]

CVE-2024-2201: Mitigations for the native BHI hardware vulnerabilty

Announce: https://www.vusec.net/projects/native-bhi/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in the master branch.

For vulnerability detail, please see:
https://vusec.net/projects/native-bhi
https://vusec.net/projects/bhi-spectre-bhb

Fixed status
mainline: [0cd01ac5dcb1e18eb18df0f0d05b5de76522a437,
1e3ad78334a69b36e107232e337f9d693dcc9df2,
  7390db8aea0d64e9deb28b8e1ce716f5020c7ee5,
0f4a837615ff925ba62648d280a861adf1582df7,
  be482ff9500999f56093738f9219bbabc729d163,
ec9404e40e8f36421a2b66ecb76dc2209fe7f3ef,
  95a6ccbdc7199a14b71ad8901cb788ba7fb5167b,
ed2e8d49b54d677f3123668a21a57822d679651f]
stable/5.15: [276fb9a658d0f44bc2e11b5f838cbe4e5759a223,
55516b355b0c6c747fa89edc53f10cf4b03441ef,
  bd53ec80f21839cfd4d852a6088279d602d67e5b,
a9ca0e34a406b5e122ad1e9b7e12a4281fccfca1,
  aa6247c9da2571afafd2bf7c709b0535f66d3900,
f825494f2c6fab421c5c59b5def321775c825818,
  c2b9e038896f01ba4bec87cfc97573b7f1b736d6,
a976b129dc868561f6cbb5e2dafe2345f32450e8]
stable/6.1: [fd52c0397b53ebcd4931981b3bc38f3b760b74df,
74fcb181772e5b8a8f1244c7393c56ae6d03c330,
  07dbb10f153f483e8249acebdffedf922e2ec2e1,
29c50bb6fbe4598d313ddb7ddb183e8b3d7bdf80,
  42196bdec0824900b02bc21e02e9bb139197ca14,
bb8384b6dfbc49be230071d1e844a8741982b1ec,
  43704e993ae54b8caf821501229dd2534ecb0e56,
3e4283b77107d1105a378859eb196e3ba5661270,
  e21838dfd0844b093a92d4cdd4db836b473c912d]
stable/6.6: [108feca9e47df1bed26ac7b04306587d9ebccda3,
eb0f175b34287f886019b86ac2f410df331d2c34,
  eb36b0dce2138581bc6b5e39d0273cb4c96ded81,
c6e3d590d0514612d96c572cba66ae0cb4b505a2,
  118794d0a572c7a8514dc774e68b59d41857b81c,
d414b401f9539858574a19af4ffc0fc0d53bfb8f,
  1c42ff893a8fb802dd90ca06af928826fdf0d16b,
cb238e95ee72a64e53a4f93181aae634cc0d3be6,
  6d9ef0c36980ef051cb55aeefb6438429e37268a]
stable/6.8: [36264ae643789d014a81bc9427797a5af607150e,
33257e28bf6d8691a040b7f1f5cd13997539f717,
  8f51637712e4da5be410a1666f8aee0d86eef898,
aec26bd00ed73c21f8f98b3e1667bc4cf016a9cf,
  a96b54b4b839536b8ffa81ec0b831d3106243a23,
a39bfa52671beb750fa2e1c7400469cde9c8ff9f,
  2bf604dc494f9f747eee62e7d46b2c179aa243dc,
15d6de3746ed724b93aca6c16e1ada68d379cb48]


CVE-2024-25742: Instruction raise #VC exception at exit

Announce: https://www.amd.com/en/resources/product-security/bulletin/amd-sb-3008.html
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in 6.9-rc1.
This bug is AMD CPU specific.
CVE-2024-25742 and CVE-2024-25743 were fixed by same commits. However,
there is no information about difference between CVE-2024-25742 and
CVE-2024-25743 yet.

Fixed status
mainline: [b82a8dbd3d2f4563156f7150c6f2ecab6e960b30,
be5341eb0d43b1e754799498bd2e8756cc167a41,
  55617fb991df535f953589586468612351575704,
f4116bfc44621882556bbf70f5284fbf429a5cf6,
  e3ef461af35a8c74f2f4ce6616491ddb355a208f]
stable/6.1: [b8ec27ae221eee458b15b700706db311474ac619,
d5f999317e83efc07b8a7d26f9556b1271a6d373,
  e09d243a518b5634201f88a5d894e8dc4d37215c,
cde700ceb0eaad67792fb2c22f44bf8a08e548f5]
stable/6.6: [34c686e5be2fa1c03ae09568159a9ef37d1c7cf5,
4591766ff6552339fbaa3d3c71814faef1988c2f,
  22ca647c8f880f21881e9b2d38070dc61196a39d,
239bff0171a86e1bafd7da03631d74df1dfec6f1]

CVE-2024-25743: Instruction raise #VC exception at exit

Announce:
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in 6.9-rc1.
This bug is AMD CPU specific.
CVE-2024-25742 and CVE-2024-25743 were fixed by same commits. However,
there is no information about difference between CVE-2024-25742 and
CVE-2024-25743 yet.

Fixed status
mainline: [b82a8dbd3d2f4563156f7150c6f2ecab6e960b30,
be5341eb0d43b1e754799498bd2e8756cc167a41,
  55617fb991df535f953589586468612351575704,
f4116bfc44621882556bbf70f5284fbf429a5cf6,
e3ef461af35a8c74f2f4ce6616491ddb355a208f]
stable/6.1: [b8ec27ae221eee458b15b700706db311474ac619,
d5f999317e83efc07b8a7d26f9556b1271a6d373,
  e09d243a518b5634201f88a5d894e8dc4d37215c,
cde700ceb0eaad67792fb2c22f44bf8a08e548f5]
stable/6.6: [34c686e5be2fa1c03ae09568159a9ef37d1c7cf5,
4591766ff6552339fbaa3d3c71814faef1988c2f,
  22ca647c8f880f21881e9b2d38070dc61196a39d,239bff0171a86e1bafd7da03631d74df1dfec6f1]

CVE-2021-47181: usb: musb: tusb6010: check return value after calling
platform_get_resource()

Announce: https://lore.kernel.org/linux-cve-announce/2024041029-CVE-2021-47181-13bb@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v5.16-rc1.

Fixed status
cip/4.4: [1ba7605856e05fa991d4654ac69e5ace66c767b9]
cip/4.4-rt: [1ba7605856e05fa991d4654ac69e5ace66c767b9]
cip/4.4-st: [1ba7605856e05fa991d4654ac69e5ace66c767b9]
mainline: [14651496a3de6807a17c310f63c894ea0c5d858e]
stable/4.19: [f87a79c04a33ab4e5be598c7b0867e6ef193d702]
stable/4.4: [1ba7605856e05fa991d4654ac69e5ace66c767b9]
stable/5.10: [679eee466d0f9ffa60a2b0c6ec19be5128927f04]
stable/5.15: [06cfb4cb2241e704d72e3045cf4d7dfb567fbce0]
stable/5.4: [3ee15f1af17407be381bcf06a78fa60b471242dd]

CVE-2021-47182: scsi: core: Fix scsi_mode_sense() buffer length handling

Announce: https://lore.kernel.org/linux-cve-announce/2024041032-CVE-2021-47182-377e@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v5.16-rc1.
It seems as if all stable kernels are affected.

Fixed status
mainline: [17b49bcbf8351d3dbe57204468ac34f033ed60bc]
stable/5.15: [e15de347faf4a9f494cbd4e9a623d343dc1b5851]

CVE-2021-47183: scsi: lpfc: Fix link down processing to address NULL
pointer dereference

Announce: https://lore.kernel.org/linux-cve-announce/2024041033-CVE-2021-47183-e130@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v5.16-rc1.
It looks as if commit db7531d2 ("scsi: lpfc: Convert abort handling to
SLI-3 and SLI-4 handlers") introduced by this issue.

Fixed status
mainline: [1854f53ccd88ad4e7568ddfafafffe71f1ceb0a6]
stable/5.15: [28de48a7cea495ab48082d9ff4ef63f7cb4e563a]

CVE-2021-47184: i40e: Fix NULL ptr dereference on VSI filter sync

Announce: https://lore.kernel.org/linux-cve-announce/2024041033-CVE-2021-47184-7544@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 41c445f ("i40e: main driver core") in v3.12-rc1.
Fixed in v5.16-rc2.

Fixed status
mainline: [37d9e304acd903a445df8208b8a13d707902dea6]
stable/4.19: [87c421ab4a43433cb009fea44bbbc77f46913e1d]
stable/5.10: [f866513ead4370402428ef724b03c3312295c178]
stable/5.15: [e91e8427a1e1633a0261e3bb0201c836ac5b3890]
stable/5.4: [c30162da91327e4cdf7cd03079f096bb3654738c]

CVE-2021-47185: tty: tty_buffer: Fix the softlockup issue in flush_to_ldisc

Announce: https://lore.kernel.org/linux-cve-announce/2024041033-CVE-2021-47185-c363@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v5.16-rc1.

Fixed status
cip/4.4: [0380f643f3a7a61b0845cdc738959c2ad5735d61]
cip/4.4-rt: [0380f643f3a7a61b0845cdc738959c2ad5735d61]
cip/4.4-st: [0380f643f3a7a61b0845cdc738959c2ad5735d61]
mainline: [3968ddcf05fb4b9409cd1859feb06a5b0550a1c1]
stable/4.19: [4f300f47dbcf9c3d4b2ea76c8554c8f360400725]
stable/4.4: [0380f643f3a7a61b0845cdc738959c2ad5735d61]
stable/5.10: [77e9fed33056f2a88eba9dd4d2d5412f0c7d1f41]
stable/5.15: [5c34486f04700f1ba04907231dce0cc2705c2d7d]
stable/5.4: [d491c84df5c469dd9621863b6a770b3428137063]

CVE-2021-47186: tipc: check for null after calling kmemdup

Announce: https://lore.kernel.org/linux-cve-announce/2024041033-CVE-2021-47186-7287@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v5.16-rc2.
It looks as if it was introduced by commit 1ef6f7c939 ("tipc: add
automatic session key exchange") in 5.10-rc1.

Fixed status
mainline: [3e6db079751afd527bf3db32314ae938dc571916]
stable/5.10: [a7d91625863d4ffed63b993b5e6dc1298b6430c9]
stable/5.15: [9404c4145542c23019a80ab1bb2ecf73cd057b10]

CVE-2021-47187: arm64: dts: qcom: msm8998: Fix CPU/L2 idle state
latency and residency

Announce: https://lore.kernel.org/linux-cve-announce/2024041034-CVE-2021-47187-b158@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v5.16-rc1.
It looks as if it was introduced by commit c3083c8 ("arm64: dts: qcom:
msm8998: Add PSCI cpuidle low power states") in 5.3-rc1.

Fixed status
mainline: [3f1dcaff642e75c1d2ad03f783fa8a3b1f56dd50]
stable/5.10: [e52fecdd0c142b95c720683885b06ee3f0e065c8]
stable/5.15: [118c826ef8b43efe0fda8faf419673707ee8c5e5]
stable/5.4: [a14d7038ea201c5526375becfc43b9ba281b1e82]

CVE-2021-47188: scsi: ufs: core: Improve SCSI abort handling

Announce: https://lore.kernel.org/linux-cve-announce/2024041034-CVE-2021-47188-092a@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 7a3e97b ("[SCSI] ufshcd: UFS Host controller
driver") in v3.4-rc1.
Fixed in v5.16-rc2.
Backporting the fix to 4.4, 4.19, 5.4, and 5.10 were failed.
- 4.4: https://lore.kernel.org/stable/164302218723442@kroah.com/
- 4.19: https://lore.kernel.org/stable/1643022186182229@kroah.com/
- 5.4: https://lore.kernel.org/stable/164302218620219@kroah.com/
- 5.10: https://lore.kernel.org/stable/164302218510944@kroah.com/

Fixed status
mainline: [3ff1f6b6ba6f97f50862aa50e79959cc8ddc2566]
stable/5.15: [c36baca06efa833adaefba61f45fefdc49b6d070]

CVE-2021-47189: btrfs: fix memory ordering between normal and ordered
work functions

Announce: https://lore.kernel.org/linux-cve-announce/2024041034-CVE-2021-47189-a3f4@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 08a9ff3 ("btrfs: Added btrfs_workqueue_struct
implemented ordered execution based on kernel workqueue") in
v3.15-rc1.
Fixed in v5.16-rc2.

Fixed status
cip/4.4: [bd660a20fea3ec60a49709ef5360f145ec0fe779]
cip/4.4-rt: [bd660a20fea3ec60a49709ef5360f145ec0fe779]
cip/4.4-st: [bd660a20fea3ec60a49709ef5360f145ec0fe779]
mainline: [45da9c1767ac31857df572f0a909fbe88fd5a7e9]
stable/4.19: [ed058d735a70f4b063323f1a7bb33cda0f987513]
stable/4.4: [bd660a20fea3ec60a49709ef5360f145ec0fe779]
stable/5.10: [6adbc07ebcaf8bead08b21687d49e0fc94400987]
stable/5.15: [47e6f9f69153247109042010f3a77579e9dc61ff]
stable/5.4: [670f6b3867c8f0f11e5097f353b164cecfec6179]

CVE-2021-47190: perf bpf: Avoid memory leak from perf_env__insert_btf()

Announce: https://lore.kernel.org/linux-cve-announce/2024041034-CVE-2021-47190-0261@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 3792cb2 ("perf bpf: Save BTF in a rbtree in
perf_env") in v5.1-rc2.
Fixed in v5.16-rc1.

Fixed status
mainline: [4924b1f7c46711762fd0e65c135ccfbcfd6ded1f]
stable/5.10: [11589d3144bc4e272e0aae46ce8156162e99babc]
stable/5.15: [ab7c3d8d81c511ddfb27823fb07081c96422b56e]
stable/5.4: [642fc22210a5e59d40b1e4d56d21ec3effd401f2]

CVE-2021-47191: scsi: scsi_debug: Fix out-of-bound read in resp_readcap16()

Announce: https://lore.kernel.org/linux-cve-announce/2024041034-CVE-2021-47191-ec4f@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v5.16-rc1.

Fixed status
mainline: [4e3ace0051e7e504b55d239daab8789dd89b863c]
stable/5.10: [3e20cb072679bdb47747ccc8bee3233a4cf0765a]
stable/5.15: [5b8bed6464ad6653586e30df046185fd816ad999]

CVE-2021-47192: scsi: core: sysfs: Fix hang when device state is set via sysfs

Announce: https://lore.kernel.org/linux-cve-announce/2024041035-CVE-2021-47192-3d45@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit f0f82e2 ("scsi: core: Fix capacity set to zero
after offlinining device") in v5.14-rc5.
Fixed in v5.16-rc2.
Linux 4.19 and 5.4 both use get_unaligned_be32() to get alloc_len
value so they seem to be affected.
Linux 4.4 calculates alloc_len value in the resp_readcap16(). It might
be nice to apply the fix.

Fixed status
mainline: [4edd8cd4e86dd3047e5294bbefcc0a08f66a430f]
stable/5.10: [a792e0128d232251edb5fdf42fb0f9fbb0b44a73]
stable/5.15: [bcc0e3175a976b7fa9a353960808adb0bb49ead8]
stable/5.4: [edd783162bf2385b43de6764f2d4c6e9f4f6be27]

CVE-2021-47193: scsi: pm80xx: Fix memory leak during rmmod

Announce: https://lore.kernel.org/linux-cve-announce/2024041035-CVE-2021-47193-c4b0@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v5.16-rc1.
It looks as if it was intorudced by commit 5a141315 ("csi: pm80xx:
Increase the number of outstanding I/O supported to 1024") in
5.10-rc1.

Fixed status
mainline: [51e6ed83bb4ade7c360551fa4ae55c4eacea354b]
stable/5.15: [269a4311b15f68d24e816f43f123888f241ed13d]

CVE-2021-47194: cfg80211: call cfg80211_stop_ap when switch from P2P_GO type

Announce: https://lore.kernel.org/linux-cve-announce/2024041035-CVE-2021-47194-51cd@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit ac80014 ("cfg80211: .stop_ap when interface is
going down") in v3.6-rc1.
Fixed in v5.16-rc2.

Fixed status
cip/4.4: [8f06bb8c216bcd172394f61e557727e691b4cb24]
cip/4.4-rt: [8f06bb8c216bcd172394f61e557727e691b4cb24]
cip/4.4-st: [8f06bb8c216bcd172394f61e557727e691b4cb24]
mainline: [563fbefed46ae4c1f70cffb8eb54c02df480b2c2]
stable/4.19: [b8a045e2a9b234cfbc06cf36923886164358ddec]
stable/4.4: [8f06bb8c216bcd172394f61e557727e691b4cb24]
stable/5.10: [7b97b5776daa0b39dbdadfea176f9cc0646d4a66]
stable/5.15: [5a9b671c8d74a3e1b999e7a0c7f366079bcc93dd]
stable/5.4: [52affc201fc22a1ab9a59ef0ed641a9adfcb8d13]

CVE-2021-47195: spi: fix use-after-free of the add_lock mutex

Announce: https://lore.kernel.org/linux-cve-announce/2024041035-CVE-2021-47195-38e8@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 6098475 ("spi: Fix deadlock when adding SPI
controllers on SPI buses") in v5.15-rc6.
Fixed in v5.16-rc2.

Fixed status
mainline: [6c53b45c71b4920b5e62f0ea8079a1da382b9434]
stable/5.15: [37330f37f6666c7739a44b2b6b95b047ccdbed2d]

CVE-2021-47196: RDMA/core: Set send and receive CQ before forwarding
to the driver

Announce: https://lore.kernel.org/linux-cve-announce/2024041036-CVE-2021-47196-d1b8@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 514aee6 ("RDMA: Globally allocate and release QP
memory") in v5.15-rc1.
Fixed in v5.16-rc2.

Fixed status
mainline: [6cd7397d01c4a3e09757840299e4f114f0aa5fa0]
stable/5.15: [b70e072feffa0ba5c41a99b9524b9878dee7748e]

CVE-2021-47197: net/mlx5e: nullify cq->dbg pointer in mlx5_debug_cq_remove()

Announce: https://lore.kernel.org/linux-cve-announce/2024041036-CVE-2021-47197-aaec@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 94b960b ("net/mlx5e: Fix memory leak in
mlx5_core_destroy_cq() error path") in v5.15-rc6.
Fixed in v5.16-rc2.

Fixed status
mainline: [76ded29d3fcda4928da8849ffc446ea46871c1c2]
stable/5.10: [471c492890557bd58f73314bb4ad85d5a8fd5026]
stable/5.15: [2ae38157080616a13a9fe3f0b4b6ec0070aa408a]

CVE-2021-47198: scsi: lpfc: Fix use-after-free in lpfc_unreg_rpi() routine

Announce: https://lore.kernel.org/linux-cve-announce/2024041036-CVE-2021-47198-2426@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v5.16-rc1.
The lpfc_reg_fab_ctrl_node() and lpfc_mbx_cmpl_fc_reg_login() were
introduced by commit
fe83e3b9 ("scsi: lpfc: Fix node handling for Fabric Controller and
Domain Controller") in 5.14-rc1.

Fixed status
mainline: [79b20beccea3a3938a8500acef4e6b9d7c66142f]
stable/5.15: [dbebf865b3239595c1d4dba063b122862583b52a]

CVE-2021-47199: net/mlx5e: CT, Fix multiple allocations and memleak of mod acts

Announce: https://lore.kernel.org/linux-cve-announce/2024041036-CVE-2021-47199-604a@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 1ef3018 ("net/mlx5e: CT: Support clear action")
in v5.7-rc1.
Fixed in v5.16-rc2.

Fixed status
mainline: [806401c20a0f9c51b6c8fd7035671e6ca841f6c2]
stable/5.15: [486e8de6e233ff2999493533c6259d1cb538653b]

CVE-2021-47200: drm/prime: Fix use after free in mmap with drm_gem_ttm_mmap

Announce: https://lore.kernel.org/linux-cve-announce/2024041037-CVE-2021-47200-ae55@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 9786b65 ("drm/ttm: fix mmap refcounting") in v5.5-rc1.
Fixed in v5.16-rc1.
Backporting the fix to 5.10 was failed.
- 5.10: https://lore.kernel.org/stable/163766826320226@kroah.com/

Fixed status
mainline: [8244a3bc27b3efd057da154b8d7e414670d5044f]
stable/5.15: [4f8e469a2384dfa4047145b0093126462cbb6dc0]

CVE-2021-47201: iavf: free q_vectors before queues in iavf_disable_vf

Announce: https://lore.kernel.org/linux-cve-announce/2024041037-CVE-2021-47201-d7c8@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 65c7006 ("i40evf: assign num_active_queues inside
i40evf_alloc_queues") in v4.13-rc1.
Fixed in v5.16-rc2.

Fixed status
mainline: [89f22f129696ab53cfbc608e0a2184d0fea46ac1]
stable/5.10: [78638b47132244e3934dc5dc79f6372d5ce8e98c]
stable/5.15: [9ef6589cac9a8c47f5544ccdf4c498093733bb3f]
stable/5.4: [926e8c83d4c1c2dac0026637eb0d492df876489e]

CVE-2021-47202: thermal: Fix NULL pointer dereferences in of_thermal_ functions

Announce: https://lore.kernel.org/linux-cve-announce/2024041037-CVE-2021-47202-58b2@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v5.16-rc1.
It looks as if Linux 4.x is affected.

Fixed status
mainline: [96cfe05051fd8543cdedd6807ec59a0e6c409195]
stable/5.10: [6a315471cb6a07f651e1d3adc8962730f4fcccac]
stable/5.15: [ef2590a5305e0b8e9342f84c2214aa478ee7f28e]
stable/5.4: [828f4c31684da94ecf0b44a2cbd35bbede04f0bd]

CVE-2021-47203: scsi: lpfc: Fix list_add() corruption in lpfc_drain_txq()

Announce: https://lore.kernel.org/linux-cve-announce/2024041037-CVE-2021-47203-ff72@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v5.16-rc1.

Fixed status
cip/4.4: [ad4776b5eb2e58af1226847fcd3b4f6d051674dd]
cip/4.4-rt: [ad4776b5eb2e58af1226847fcd3b4f6d051674dd]
cip/4.4-st: [ad4776b5eb2e58af1226847fcd3b4f6d051674dd]
mainline: [99154581b05c8fb22607afb7c3d66c1bace6aa5d]
stable/4.19: [b291d147d0268e93ad866f8bc820ea14497abc9b]
stable/4.4: [ad4776b5eb2e58af1226847fcd3b4f6d051674dd]
stable/5.10: [c097bd5a59162156d9c2077a2f58732ffbaa9fca]
stable/5.15: [814d3610c4ce86e8cf285b2cdac0057a42e82de5]
stable/5.4: [16bcbfb56d759c25665f786e33ec633b9508a08f]

CVE-2021-47204: net: dpaa2-eth: fix use-after-free in dpaa2_eth_remove

Announce: https://lore.kernel.org/linux-cve-announce/2024041037-CVE-2021-47204-82d1@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 7472dd9 ("staging: fsl-dpaa2/eth: Move print
message") in v4.17-rc1.
Fixed in v5.16-rc2.

Fixed status
mainline: [9b5a333272a48c2f8b30add7a874e46e8b26129c]
stable/5.10: [1c4099dc0d6a01e76e4f7dd98e4b3e0d55d80ad9]
stable/5.15: [32d4686224744819ddcae58b666c21d2a4ef4c88]
stable/5.4: [d74ff10ed2d93dc9b67e99a74b36fb9a83273d8a]

CVE-2021-47205: clk: sunxi-ng: Unregister clocks/resets when unbinding

Announce: https://lore.kernel.org/linux-cve-announce/2024041038-CVE-2021-47205-3f43@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v5.16-rc1.

following lines shows affected file name and its introduced version.
ccu-sun4i-a10.c in 4.14-rc1
ccu-sun50i-a100-r.c in 5.10-rc1
ccu-sun50i-a100.c in 5.10-rc1
ccu-sun50i-a64.c in 4.10-rc1
ccu-sun50i-h6-r.c in 4.18-rc1
ccu-sun50i-h6.c in 4.17-rc1
ccu-sun50i-h616.c in 5.12-rc1-dontuse
ccu-sun5i.c in 4.11-rc1
ccu-sun6i-a31.c in 4.9-rc1
ccu-sun8i-a23.c in 4.9-rc1
ccu-sun8i-a33.c in 4.9-rc1
ccu-sun8i-a83t.c in 4.13-rc1
ccu-sun8i-de2.c in 4.13-rc1
ccu-sun8i-h3.c in 4.8-rc1
ccu-sun8i-r.c in 4.12-rc1
ccu-sun8i-r40.c in 4.14-rc1
ccu-sun8i-v3s.c in 4.11-rc1
ccu-sun9i-a80-de.c in 4.11-rc1
ccu-sun9i-a80-usb.c in 4.11-rc1
ccu-sun9i-a80.c in 4.11-rc1
ccu-suniv-f1c100s.c in 5.0-rc1
ccu_common.c in 4.8-rc1
ccu_common.h in 4.8-rc1

Fixed status
mainline: [9bec2b9c6134052994115d2d3374e96f2ccb9b9d]
stable/5.15: [b5dd513daa70ee8f6d281a20bd28485ee9bb7db2]

CVE-2021-47206: usb: host: ohci-tmio: check return value after calling
platform_get_resource()

Announce: https://lore.kernel.org/linux-cve-announce/2024041038-CVE-2021-47206-fe4c@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v5.16-rc1.

Fixed status
cip/4.4: [28e016e02118917e50a667bc72fb80098cf2b460]
cip/4.4-rt: [28e016e02118917e50a667bc72fb80098cf2b460]
cip/4.4-st: [28e016e02118917e50a667bc72fb80098cf2b460]
mainline: [9eff2b2e59fda25051ab36cd1cb5014661df657b]
stable/4.19: [951b8239fd24678b56c995c5c0456ab12e059d19]
stable/4.4: [28e016e02118917e50a667bc72fb80098cf2b460]
stable/5.10: [2474eb7fc3bfbce10f7b8ea431fcffe5dd5f5100]
stable/5.15: [065334f6640d074a1caec2f8b0091467a22f9483]
stable/5.4: [f98986b7acb4219f95789095eced93ed69d81d35]

CVE-2021-47207: ALSA: gus: fix null pointer dereference on pointer block

Announce: https://lore.kernel.org/linux-cve-announce/2024041038-CVE-2021-47207-7ac9@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v5.16-rc1.

Fixed status
cip/4.4: [3e28e083dcdf03a18a083f8a47b6bb6b1604b5be]
cip/4.4-rt: [3e28e083dcdf03a18a083f8a47b6bb6b1604b5be]
cip/4.4-st: [3e28e083dcdf03a18a083f8a47b6bb6b1604b5be]
mainline: [a0d21bb3279476c777434c40d969ea88ca64f9aa]
stable/4.19: [ab4c1ebc40f699f48346f634d7b72b9c5193f315]
stable/4.4: [3e28e083dcdf03a18a083f8a47b6bb6b1604b5be]
stable/5.10: [1ac6cd87d8ddd36c43620f82c4d65b058f725f0f]
stable/5.15: [16721797dcef2c7c030ffe73a07f39a65f9323c3]
stable/5.4: [c6d2cefdd05c4810c416fb8d384b5c377bd977bc]

CVE-2021-47209: sched/fair: Prevent dead task groups from regaining cfs_rq's

Announce: https://lore.kernel.org/linux-cve-announce/2024041004-CVE-2021-47209-1cf6@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit a7b359f ("sched/fair: Correctly insert cfs_rq's
to list on unthrottle") in v5.13-rc7.
Fixed in v5.16-rc1.

Fixed status
mainline: [b027789e5e50494c2325cc70c8642e7fd6059479]
stable/5.15: [512e21c150c1c3ee298852660f3a796e267e62ec]

CVE-2021-47210: usb: typec: tipd: Remove WARN_ON in tps6598x_block_read

Announce: https://lore.kernel.org/linux-cve-announce/2024041004-CVE-2021-47210-1d37@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v5.16-rc1.
It looks as if it was introduced by commit 8d361fa ("usb: typec:
tps6598x: Remove VLA usage") in 4.19-rc1.

Fixed status
mainline: [b7a0a63f3fed57d413bb857de164ea9c3984bc4e]
stable/4.19: [2a897d384513ba7f7ef05611338b9a6ec6aeac00]
stable/5.10: [eff8b7628410cb2eb562ca0d5d1f12e27063733e]
stable/5.15: [2c71811c963b6c310a29455d521d31a7ea6c5b5e]
stable/5.4: [30dcfcda8992dc42f18e7d35b6a1fa72372d382d]

CVE-2021-47211: ALSA: usb-audio: fix null pointer dereference on pointer cs_desc

Announce: https://lore.kernel.org/linux-cve-announce/2024041004-CVE-2021-47211-cde3@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v5.16-rc1.

Fixed status
mainline: [b97053df0f04747c3c1e021ecbe99db675342954]
stable/5.15: [58fa50de595f152900594c28ec9915c169643739]

CVE-2021-47212: net/mlx5: Update error handler for UCTX and UMEM

Announce: https://lore.kernel.org/linux-cve-announce/2024041005-CVE-2021-47212-01d8@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 6a6fabb ("net/mlx5: Update pci error handler
entries and command translation") in v5.2-rc6.
The snd_usb_set_sample_rate_v2v3() was introduced by commit 93db51d0
("ALSA: usb-audio: Check valid altsetting at parsing rates for
UAC2/3") in 5.11-rc1.
So, prior to 5.11 is not affected.
Fixed in v5.16-rc2.

Fixed status
mainline: [ba50cd9451f6c49cf0841c0a4a146ff6a2822699]
stable/5.15: [a51a6da375d82aed5c8f83abd13e7d060421bd48]

CVE-2021-47213: NFSD: Fix exposure in nfsd4_decode_bitmap()

Announce: https://lore.kernel.org/linux-cve-announce/2024041005-CVE-2021-47213-c84f@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit d1c263a ("NFSD: Replace READ* macros in
nfsd4_decode_fattr()") in v5.11-rc1.
Fixed in v5.16-rc2.

Fixed status
mainline: [c0019b7db1d7ac62c711cda6b357a659d46428fe]
stable/5.15: [10c22d9519f3f5939de61a1500aa3a926b778d3a]

CVE-2021-47214: hugetlb, userfaultfd: fix reservation restore on
userfaultfd error

Announce: https://lore.kernel.org/linux-cve-announce/2024041005-CVE-2021-47214-59f9@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit c7b1850 ("hugetlb: don't pass page cache pages to
restore_reserve_on_error") in v5.14-rc7.
Fixed in v5.16-rc2.

Fixed status
mainline: [cc30042df6fcc82ea18acf0dace831503e60a0b7]
stable/5.15: [b5069d44e2fbc4a9093d005b3ef0949add3dd27e]

CVE-2021-47215: net/mlx5e: kTLS, Fix crash in RX resync flow

Announce: https://lore.kernel.org/linux-cve-announce/2024041005-CVE-2021-47215-2718@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit e9ce991 ("net/mlx5e: kTLS, Add resiliency to RX
resync failures") in v5.13-rc1.
Fixed in v5.16-rc2.

Fixed status
mainline: [cc4a9cc03faa6d8db1a6954bb536f2c1e63bdff6]
stable/5.15: [ebeda7a9528ae690e6bf12791a868f0cca8391f2]

CVE-2021-47216: scsi: advansys: Fix kernel pointer leak

Announce: https://lore.kernel.org/linux-cve-announce/2024041006-CVE-2021-47216-1700@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v5.16-rc1.

Fixed status
cip/4.4: [06d7d12efb5c62db9dea15141ae2b322c2719515]
cip/4.4-rt: [06d7d12efb5c62db9dea15141ae2b322c2719515]
cip/4.4-st: [06d7d12efb5c62db9dea15141ae2b322c2719515]
mainline: [d4996c6eac4c81b8872043e9391563f67f13e406]
stable/4.19: [f5a0ba4a9b5e70e7b2f767636d26523f9d1ac59d]
stable/4.4: [06d7d12efb5c62db9dea15141ae2b322c2719515]
stable/5.10: [055eced3edf5b675d12189081303f6285ef26511]
stable/5.15: [27490ae6a85a70242d80615ca74d0362a820d6a7]
stable/5.4: [cc248790bfdcf879e3094fa248c85bf92cdf9dae]

CVE-2021-47217: x86/hyperv: Fix NULL deref in set_hv_tscchange_cb() if
Hyper-V setup fails

Announce: https://lore.kernel.org/linux-cve-announce/2024041006-CVE-2021-47217-a7d0@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 9328626 ("x86/hyperv: Reenlightenment
notifications support") in v4.16-rc1.
Fixed in v5.16-rc2.

Fixed status
mainline: [daf972118c517b91f74ff1731417feb4270625a4]
stable/4.19: [b20ec58f8a6f4fef32cc71480ddf824584e24743]
stable/5.10: [9c177eee116cf888276d3748cb176e72562cfd5c]
stable/5.15: [8823ea27fff6084bbb4bc71d15378fae0220b1d8]
stable/5.4: [b0e44dfb4e4c699cca33ede431b8d127e6e8d661]

CVE-2021-47218: selinux: fix NULL-pointer dereference when hashtab
allocation fails

Announce: https://lore.kernel.org/linux-cve-announce/2024041006-CVE-2021-47218-cdc8@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 03414a4 ("selinux: do not allocate hashtabs
dynamically") in v5.8-rc1.
Fixed in v5.16-rc3.

Fixed status
mainline: [dc27f3c5d10c58069672215787a96b4fae01818b]
stable/5.10: [b17dd53cac769dd13031b0ca34f90cc65e523fab]
stable/5.15: [83c8ab8503adf56bf68dafc7a382f4946c87da79]

CVE-2021-47219: scsi: scsi_debug: Fix out-of-bound read in resp_report_tgtpgs()

Announce: https://lore.kernel.org/linux-cve-announce/2024041006-CVE-2021-47219-c09e@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v5.16-rc1.
All stable kernels look to be affected.

Fixed status
mainline: [f347c26836c270199de1599c3cd466bb7747caa9]
stable/5.10: [8440377e1a5644779b4c8d013aa2a917f5fc83c3]
stable/5.15: [66523553fa62c7878fc5441dc4e82be71934eb77]

CVE-2024-26815: net/sched: taprio: proper TCA_TAPRIO_TC_ENTRY_INDEX check

Announce: https://lore.kernel.org/linux-cve-announce/2024041006-CVE-2024-26815-7f4e@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit a54fc09 ("net/sched: taprio: allow user input of
per-tc max SDU") in v6.1-rc1.
Fixed in v6.9-rc1.

Fixed status
mainline: [343041b59b7810f9cdca371f445dd43b35c740b1]
stable/6.1: [bd2474a45df7c11412c2587de3d4e43760531418]
stable/6.6: [6915b1b28fe57e92c78e664366dc61c4f15ff03b]

CVE-2024-26816: x86, relocs: Ignore relocations in .notes section

Announce: https://lore.kernel.org/linux-cve-announce/2024041039-CVE-2024-26816-5054@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 5ead97c ("xen: Core Xen implementation") in v2.6.23-rc1.
Introduced by commit da1a679 ("Add /sys/kernel/notes") in v2.6.23-rc1.
Fixed in v6.9-rc1.

Fixed status
mainline: [aaa8736370db1a78f0e8434344a484f9fd20be3b]
stable/4.19: [13edb509abc91c72152a11baaf0e7c060a312e03]
stable/5.10: [a4e7ff1a74274e59a2de9bb57236542aa990d20a]
stable/5.15: [c7cff9780297d55d97ad068b68b703cfe53ef9af]
stable/5.4: [52018aa146e3cf76569a9b1e6e49a2b7c8d4a088]
stable/6.1: [47635b112a64b7b208224962471e7e42f110e723]
stable/6.6: [af2a9f98d884205145fd155304a6955822ccca1c]

* Updated CVEs

CVE-2023-28746: Register File Data Sampling (RFDS)

stable 5.15 was fixed.

Fixed status
mainline: [e95df4ec0c0c9791941f112db699fae794b9862a,
4e42765d1be01111df0c0275bbaf1db1acef346e,
  8076fcde016c9c0e0660543e67bff86cb48a7c9c,
2a0180129d726a4b953232175857d442651b55a0]
stable/5.15: [a2b586df5546311f9be5f6acb9fe489b623c526e,
4fa001418efd40ad00ff429e6064ab8eeeddc739,
  2fb08b672eb78c4930413cf529734792456ae15f,
2ae88e83f3b7e579a7085d140f61122f128932f1]
stable/6.1: [8b5760939db9c49c03b9e19f6c485a8812f48d83,
29476fac750dddeabc3503bf9b13e05b949d7adb,
  d405b9c03f06b1b5e73ebc4f34452687022f7029,
b2e92ab17e440a97c716b701ecd897eebca11ac0]
stable/6.6: [c35ca0968de41952af2ad7d22881e4a7c6e1b145,
ddfd38558acc5b3891fd197372fedb76372da740,
  77018fb9efe50cf24e61275ee09253cf1fbb6854,
4a5b5bfea063745471af6395d22ebaea8242225e]
stable/6.7: [18867a204511d032c2a6ed083461a10905061fac,
13acf9f1df3513ea7a5170399c2a8e297e5fbdc1,
  fe5f4d14cdad934c5c92080cebd5b18189bf4ac9,
328607cf9e1fcbbc3f5521391d601306f72a5890]
stable/6.8: [056c33c67a74aec19668b927d460825f5e9aab42,
7586a7c0ba2f16ee6fe7f1ad95313775717e9f53,
  c8a1b14f43bb89a62c1471ec2931f152b37b3782,
50d33b98b1e23d1cd8743b3cac7a0ae5718b8b00]

CVE-2023-47233: Use after Free bug in brcmf_cfg80211_detach

stable 5.15 was fixed.

Fixed status
mainline: [0f7352557a35ab7888bc7831411ec8a3cbe20d78]
stable/5.15: [8c36205123dc57349b59b4f1a2301eb278cbc731]
stable/6.1: [0b812f706fd7090be74812101114a0e165b36744]
stable/6.6: [190794848e2b9d15de92d502b6ac652806904f5a]
stable/6.7: [6678a1e7d896c00030b31491690e8ddc9a90767a]
stable/6.8: [0a7591e14a8da794d0b93b5d1c6254ccb23adacb]

CVE-2023-52488: serial: sc16is7xx: convert from _raw_ to _noinc_
regmap functions for FIFO

stable 5.15 was fixed.

Fixed status
mainline: [dbf4ab821804df071c8b566d9813083125e6d97b]
stable/5.15: [e635f652696ef6f1230621cfd89c350cb5ec6169]
stable/6.1: [416b10d2817c94db86829fb92ad43ce7d002c573]
stable/6.6: [084c24e788d9cf29c55564de368bf5284f2bb5db]
stable/6.7: [aa7cb4787698add9367b19f7afc667662c9bdb23]

CVE-2024-24857: Integer overflow bug was found in bluetooth device driver

The mainline, 5.15, 6.1, 6.6, and 6.8 were fixed.

Fixed status
mainline: [7835fcfd132eb88b87e8eb901f88436f63ab60f7]
stable/5.15: [a8170af8b10e904c0052aa4ec31c653635730d92]
stable/6.1: [18e189442a5896255e764f8e875c13d16248ef2f]
stable/6.6: [d75632d0db3cdc31873d25756066a7f56bc87737]
stable/6.8: [d0bfebd8ca411697248d0cebe4ad2649f23ab0bf]

CVE-2024-24858: Race condition bug in bluetooth driver causes DoS

The mainline, 5.15, 6.1, 6.6, and 6.8 were fixed.

Fixed status
mainline: [7835fcfd132eb88b87e8eb901f88436f63ab60f7]
stable/5.15: [a8170af8b10e904c0052aa4ec31c653635730d92]
stable/6.1: [18e189442a5896255e764f8e875c13d16248ef2f]
stable/6.6: [d75632d0db3cdc31873d25756066a7f56bc87737]
stable/6.8: [d0bfebd8ca411697248d0cebe4ad2649f23ab0bf]

CVE-2024-24861: Race condition bug was found in media/xc4000 device
driver in xc4000 xc4000_get_frequency()

stable 5.15 was fixed.

Fixed status
mainline: [36d503ad547d1c75758a6fcdbec2806f1b6aeb41]
stable/5.15: [fec51819607ff0a80ad8ce678120fda80ca0b2fa]
stable/6.1: [09c1be4d581d3356159abcc5a8a7a6c5f1bf1e77]
stable/6.6: [dc5e4f240473b64f7b2f24424e96c92435ebd8d7]
stable/6.7: [b0864de231dece0f7226b909521bebc86105743a]
stable/6.8: [5c26122885cedcb99606cdc06a3419db7feb1e1e]

CVE-2024-26629: nfsd: fix RELEASE_LOCKOWNER

stable 5.15 was fixed.

Fixed status
mainline: [edcf9725150e42beeca42d085149f4c88fa97afd]
stable/5.15: [c6f8b3fcc62725e4129f2c0fd550d022d4a7685a]
stable/6.1: [e4cf8941664cae2f89f0189c29fe2ce8c6be0d03]
stable/6.6: [b7d2eee1f53899b53f069bba3a59a419fc3d331b]
stable/6.7: [8f5b860de87039b007e84a28a5eefc888154e098]

CVE-2024-26642: netfilter: nf_tables: disallow anonymous set with timeout flag

stable 5.15 was fixed.

Fixed status
mainline: [16603605b667b70da974bea8216c93e7db043bf1]
stable/5.15: [7cdc1be24cc1bcd56a3e89ac4aef20e31ad09199]
stable/6.1: [72c1efe3f247a581667b7d368fff3bd9a03cd57a]
stable/6.6: [c0c2176d1814b92ea4c8e7eb7c9cd94cd99c1b12]
stable/6.7: [8e07c16695583a66e81f67ce4c46e94dece47ba7]

CVE-2024-26643: netfilter: nf_tables: mark set as dead when unbinding
anonymous set with timeout

stable 5.15 was fixed.

Fixed status
mainline: [552705a3650bbf46a22b1adedc1b04181490fc36]
stable/5.15: [291cca35818bd52a407bc37ab45a15816039e363]
stable/6.1: [406b0241d0eb598a0b330ab20ae325537d8d8163]
stable/6.6: [b2d6f9a5b1cf968f1eaa71085ceeb09c2cb276b1]
stable/6.7: [5224afbc30c3ca9ba23e752f0f138729b2c48dd8]

CVE-2024-26654: ALSA: sh: aica: reorder cleanup operations to avoid UAF bugs

stable 5.15 was fixed.

Fixed status
mainline: [051e0840ffa8ab25554d6b14b62c9ab9e4901457]
stable/5.15: [8c990221681688da34295d6d76cc2f5b963e83f5]
stable/6.1: [9d66ae0e7bb78b54e1e0525456c6b54e1d132046]
stable/6.6: [61d4787692c1fccdc268ffa7a891f9c149f50901]
stable/6.7: [e955e8a7f38a856fc6534ba4e6bffd4d5cc80ac3]
stable/6.8: [3c907bf56905de7d27b329afaf59c2fb35d17b04]

CVE-2024-26687: xen/events: close evtchn after mapping cleanup

Fixed status
mainline: [fa765c4b4aed2d64266b694520ecb025c862c5a9]
stable/5.15: [ea592baf9e41779fe9a0424c03dd2f324feca3b3]
stable/6.1: [585a344af6bcac222608a158fc2830ff02712af5]
stable/6.6: [20980195ec8d2e41653800c45c8c367fa1b1f2b4]
stable/6.7: [9be71aa12afa91dfe457b3fb4a444c42b1ee036b]

Currently tracking CVEs

CVE-2021-31615: Unencrypted Bluetooth Low Energy baseband links in
Bluetooth Core Specifications 4.0 through 5.2

There is no fix information.

CVE-2020-26556: kernel: malleable commitment Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26557: kernel: predictable Authvalue in Bluetooth Mesh
Provisioning Leads to MITM

No fix information.

CVE-2020-26559: kernel: Authvalue leak in Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26560: kernel: impersonation attack in Bluetooth Mesh Provisioning

No fix information.

Regards,
-- 
Masami Ichikawa
Cybertrust Japan Co., Ltd.

Email :masami.ichikawa@cybertrust.co.jp
          :masami.ichikawa@miraclelinux.com


^ permalink raw reply	[flat|nested] 33+ messages in thread

* [kernel-cve-report] New CVE entries this week
@ 2024-04-04  5:34 Masami Ichikawa
  0 siblings, 0 replies; 33+ messages in thread
From: Masami Ichikawa @ 2024-04-04  5:34 UTC (permalink / raw)
  To: cip-dev

Hi!

It's this week's CVE report.

This week reported 137 new CVEs and 12 updated CVEs.

* New CVEs

CVE-2023-52628: netfilter: nftables: exthdr: fix 4-byte stack OOB write

Announce: https://lore.kernel.org/linux-cve-announce/2024032850-CVE-2023-52628-14fb@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 49499c3 ("netfilter: nf_tables: switch registers
to 32 bit addressing") in v4.1-rc1.
Introduced by commit 935b7f6 ("netfilter: nft_exthdr: add TCP option
matching") in v4.11-rc1.
Introduced by commit 133dc20 ("netfilter: nft_exthdr: Support SCTP
chunks") in v5.14-rc1.
Introduced by commit dbb5281 ("netfilter: nf_tables: add support for
matching IPv4 options") in v5.3-rc1.
Fixed in v6.6-rc1.

For more detail, please check the following urls.

- ZDI-CAN-21950/ZDI-24-298:
https://www.zerodayinitiative.com/advisories/ZDI-24-298/
- ZDI-CAN-21951/ZDI-24-299:
https://www.zerodayinitiative.com/advisories/ZDI-24-299/
- ZDI-CAN-21961/ZDI-24-297:
https://www.zerodayinitiative.com/advisories/ZDI-24-297/

Fixed status
mainline: [fd94d9dadee58e09b49075240fe83423eb1dcd36]
stable/5.10: [a7d86a77c33ba1c357a7504341172cc1507f0698]
stable/5.15: [1ad7b189cc1411048434e8595ffcbe7873b71082]
stable/6.1: [d9ebfc0f21377690837ebbd119e679243e0099cc]

CVE-2023-52629: sh: push-switch: Reorder cleanup operations to avoid
use-after-free bug

Announce: https://lore.kernel.org/linux-cve-announce/2024032949-CVE-2023-52629-a508@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 9f5e8ee ("sh: generic push-switch framework.") in
v2.6.20.16.
This bug is only affected by SH architecture.
Fixed in v6.6-rc1.

Fixed status
mainline: [246f80a0b17f8f582b2c0996db02998239057c65]

CVE-2024-26653: usb: misc: ljca: Fix double free in error handling path

Announce: https://lore.kernel.org/linux-cve-announce/2024040122-CVE-2024-26653-7903@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit acd6199 ("usb: Add support for Intel LJCA
device") in v6.7-rc1.
Thic commit is not backported to older stable kernels.
Fixed in v6.9-rc2.

Fixed status
mainline: [7c9631969287a5366bc8e39cd5abff154b35fb80]
stable/6.7: [420babea4f1881a7c4ea22a8e218b8c6895d3f21]
stable/6.8: [8a9f653cc852677003c23ee8075e3ed8fb4743c9]

CVE-2024-26654: ALSA: sh: aica: reorder cleanup operations to avoid UAF bugs

Announce: https://lore.kernel.org/linux-cve-announce/2024040142-CVE-2024-26654-aa6c@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 198de43 ("[ALSA] Add ALSA support for the SEGA
Dreamcast PCM device") in v2.6.23-rc1.
Fixed in v6.9-rc2.

Fixed status
mainline: [051e0840ffa8ab25554d6b14b62c9ab9e4901457]
stable/6.1: [9d66ae0e7bb78b54e1e0525456c6b54e1d132046]
stable/6.6: [61d4787692c1fccdc268ffa7a891f9c149f50901]
stable/6.7: [e955e8a7f38a856fc6534ba4e6bffd4d5cc80ac3]
stable/6.8: [3c907bf56905de7d27b329afaf59c2fb35d17b04]

CVE-2024-26655: Fix memory leak in posix_clock_open()

Announce: https://lore.kernel.org/linux-cve-announce/2024040124-CVE-2024-26655-265a@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 60c6946 ("posix-clock: introduce
posix_clock_context concept") in v6.7-rc1.
Thic commit is not backported to older stable kernels.
Fixed in v6.9-rc2.

Fixed status
mainline: [5b4cdd9c5676559b8a7c944ac5269b914b8c0bb8]
stable/6.7: [a88649b49523e8cbe95254440d803e38c19d2341]
stable/6.8: [0200dd7ed2335469955d7e69cc1a6fa7df1f3847]

CVE-2023-52630: blk-iocost: Fix an UBSAN shift-out-of-bounds warning

Announce: https://lore.kernel.org/linux-cve-announce/2024040219-CVE-2023-52630-a529@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 5160a5a ("blk-iocost: implement delay adjustment
hysteresis") in v5.10-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc4.

Fixed status
mainline: [2a427b49d02995ea4a6ff93a1432c40fa4d36821]
stable/5.10: [9f56f38331171c9a19754004f0664686d67ee48d]
stable/5.15: [1e4d3f8bd880e02932a9ea179f90bfa74fd2e899]
stable/6.1: [e5dc63f01e027721c29f82069f7e97e2149fa131]
stable/6.6: [27b216130e64651e76ed583742a1b4e4d08a67c3]
stable/6.7: [cd33b330cb21675189e747953845f5c3689e4912]

CVE-2023-52631: fs/ntfs3: Fix an NULL dereference bug

Announce: https://lore.kernel.org/linux-cve-announce/2024040222-CVE-2023-52631-ea7b@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit be71b5c ("fs/ntfs3: Add attrib operations") in v5.15-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc4.

Fixed status
mainline: [b2dd7b953c25ffd5912dda17e980e7168bebcf6c]
stable/5.15: [ae4acad41b0f93f1c26cc0fc9135bb79d8282d0b]
stable/6.1: [ec1bedd797588fe38fc11cba26d77bb1d9b194c6]
stable/6.6: [fb7bcd1722bc9bc55160378f5f99c01198fd14a7]
stable/6.7: [686820fe141ea0220fc6fdfc7e5694f915cf64b2]

CVE-2023-52632: drm/amdkfd: Fix lock dependency warning with srcu

Announce: https://lore.kernel.org/linux-cve-announce/2024040218-CVE-2023-52632-f7bb@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc1.
It looks as if this bug was introduced by commit 367c9b0 ("drm/amdkfd:
Ensure mm remain valid in svm deferred_list work") in 5.18-rc1.

Fixed status
mainline: [2a9de42e8d3c82c6990d226198602be44f43f340]
stable/6.1: [b602f098f716723fa5c6c96a486e0afba83b7b94]
stable/6.6: [752312f6a79440086ac0f9b08d7776870037323c]
stable/6.7: [1556c242e64cdffe58736aa650b0b395854fe4d4]

CVE-2023-52633: um: time-travel: fix time corruption

Announce: https://lore.kernel.org/linux-cve-announce/2024040218-CVE-2023-52633-d020@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc1.
The time travel mode was introduced by commit 06503870 ("um: Support
time travel mode") in 5.3-rc1.
The time_travel_ndelay() was introduced by 0bc8fb4d ("um: Implement
ndelay/udelay in time-travel mode") in 5.7-rc1.
So,  Linux 4.x is not affected.

Fixed status
mainline: [abe4eaa8618bb36c2b33e9cdde0499296a23448c]
stable/5.15: [0c7478a2da3f5fe106b4658338873d50c86ac7ab]
stable/6.1: [4f7dad73df4cdb2b7042103d3922745d040ad025]
stable/6.6: [de3e9d8e8d1ae0a4d301109d1ec140796901306c]
stable/6.7: [b427f55e9d4185f6f17cc1e3296eb8d0c4425283]

CVE-2023-52634: drm/amd/display: Fix disable_otg_wa logic

Announce: https://lore.kernel.org/linux-cve-announce/2024040219-CVE-2023-52634-27e0@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc1.
Vulnerable function dcn35_disable_otg_wa() was introduced by commit
8774029f76 ("drm/amd/display: Add DCN35 CLK_MGR") in 6.7-rc1.

Fixed status
mainline: [2ce156482a6fef349d2eba98e5070c412d3af662]
stable/6.7: [ce29728ef6485a367934cc100249c66dd3cde5b6]

CVE-2023-52635: PM / devfreq: Synchronize devfreq_monitor_[start/stop]

Announce: https://lore.kernel.org/linux-cve-announce/2024040219-CVE-2023-52635-8b18@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc1.
The delayed timer feature was introduced by commit 4dc3bab8 ("PM /
devfreq: Add support delayed timer for polling mode") in 5.9-rc1.

Fixed status
mainline: [aed5ed595960c6d301dcd4ed31aeaa7a8054c0c6]
stable/5.10: [3399cc7013e761fee9d6eec795e9b31ab0cbe475]
stable/5.15: [099f6a9edbe30b142c1d97fe9a4748601d995675]
stable/6.1: [31569995fc65007b73a3fff605ec2b3401b435e9]
stable/6.6: [0aedb319ef3ed39e9e5a7b7726c8264ca627bbd9]
stable/6.7: [ae815e2fdc284ab31651d52460698bd89c0fce22]

CVE-2023-52636: libceph: just wait for more data to be available on the socket

Announce: https://lore.kernel.org/linux-cve-announce/2024040249-CVE-2023-52636-d965@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit d396f89 ("libceph: add sparse read support to
msgr1") in v6.6-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc4.

Fixed status
mainline: [8e46a2d068c92a905d01cbb018b00d66991585ab]
stable/6.6: [da9c33a70f095d5d55c36d0bfeba969e31de08ae]
stable/6.7: [bd9442e553ab8bf74b8be3b3c0a43bf4af4dc9b8]

CVE-2024-26656: drm/amdgpu: fix use-after-free bug

Announce: https://lore.kernel.org/linux-cve-announce/2024040247-CVE-2024-26656-ffaa@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.9-rc1.
It looks as if commit 62914a99 ("drm/amdgpu: Use mmu_interval_insert
instead of hmm_mirror") in 5.5-rc1 or
81fa1af31 ("drm/amdgpu: Use mmu_interval_notifier instead of
hmm_mirror") in 5.5-rc1 are suspicious.
So, prior to Linux 5.5 may not be affected.

Fixed status
mainline: [22207fd5c80177b860279653d017474b2812af5e]
stable/6.6: [e87e08c94c9541b4e18c4c13f2f605935f512605]
stable/6.7: [af054a5fb24a144f99895afce9519d709891894c]
stable/6.8: [22f665ecfd1225afa1309ace623157d12bb9bb0c]

CVE-2024-26657: drm/sched: fix null-ptr-deref in init entity

Announce: https://lore.kernel.org/linux-cve-announce/2024040250-CVE-2024-26657-25a0@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 56e4496 ("drm/sched: Convert the GPU scheduler to
variable number of run-queues") in v6.7-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.9-rc2.

Fixed status
mainline: [f34e8bb7d6c6626933fe993e03ed59ae85e16abb]
stable/6.7: [74cd204c7afe498aa9dcc3ebf0ecac53d477a429]
stable/6.8: [54b5b7275dfdec35812ccce70930cd7c4ee612b2]

CVE-2024-26658: bcachefs: grab s_umount only if snapshotting

Announce: https://lore.kernel.org/linux-cve-announce/2024040222-CVE-2024-26658-1451@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc1.
According to the commit log, commit 42d23732 ("bcachefs: Snapshot
creation, deletion") may introduce this bug.

Fixed status
mainline: [2acc59dd88d27ad69b66ded80df16c042b04eeec]
stable/6.7: [5b41d3fd04c6757b9c2a60a0c5b2609cae9999df]

CVE-2024-26659: xhci: handle isoc Babble and Buffer Overrun events properly

Announce: https://lore.kernel.org/linux-cve-announce/2024040222-CVE-2024-26659-e4f6@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc3.
Backporting this fix to 4.19
(https://lore.kernel.org/stable/2024021310-prelaunch-earmark-e533@gregkh/)
and
5.4 (https://lore.kernel.org/stable/2024021309-hypertext-gush-3da8@gregkh/)
were failed.
It looks like 4.x kernels are affected.

Fixed status
mainline: [7c4650ded49e5b88929ecbbb631efb8b0838e811]
stable/5.10: [696e4112e5c1ee61996198f0ebb6ca3fab55166e]
stable/5.15: [2aa7bcfdbb46241c701811bbc0d64d7884e3346c]
stable/6.1: [2e3ec80ea7ba58bbb210e83b5a0afefee7c171d3]
stable/6.6: [f5e7ffa9269a448a720e21f1ed1384d118298c97]
stable/6.7: [418456c0ce56209610523f21734c5612ee634134]

CVE-2024-26660: drm/amd/display: Implement bounds check for stream
encoder creation in DCN301

Announce: https://lore.kernel.org/linux-cve-announce/2024040222-CVE-2024-26660-3f40@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 3a83e4e ("drm/amd/display: Add dcn3.01 support to
DC (v2)") in v5.11-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc4.

Fixed status
mainline: [58fca355ad37dcb5f785d9095db5f748b79c5dc2]
stable/5.15: [42442f74314d41ddc68227047036fa3e78940054]
stable/6.1: [efdd665ce1a1634b8c1dad5e7f6baaef3e131d0a]
stable/6.6: [cd9bd10c59e3c1446680514fd3097c5b00d3712d]
stable/6.7: [a938eab9586eea31cfd129a507f552efae14d738]

CVE-2024-26661: drm/amd/display: Add NULL test for 'timing generator'
in 'dcn21_set_pipe()'

Announce: https://lore.kernel.org/linux-cve-announce/2024040223-CVE-2024-26661-bef6@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 474ac4a ("drm/amd/display: Implement some asic
specific abm call backs.") in v5.9-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc4.

Fixed status
mainline: [66951d98d9bf45ba25acf37fe0747253fafdf298]
stable/6.6: [3f3c237a706580326d3b7a1b97697e5031ca4667]
stable/6.7: [39f24c08363af1cd945abad84e3c87fd3e3c845a]

CVE-2024-26662: drm/amd/display: Fix 'panel_cntl' could be null in
'dcn21_set_backlight_level()'

Announce: https://lore.kernel.org/linux-cve-announce/2024040223-CVE-2024-26662-863c@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 474ac4a ("drm/amd/display: Implement some asic
specific abm call backs.") in v5.9-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc4.

Fixed status
mainline: [e96fddb32931d007db12b1fce9b5e8e4c080401b]
stable/6.6: [2e150ccea13129eb048679114808eb9770443e4d]
stable/6.7: [0c863cab0e9173f8b6c7bc328bee3b8625f131b5]

CVE-2024-26663: tipc: Check the bearer type before calling
tipc_udp_nl_bearer_add()

Announce: https://lore.kernel.org/linux-cve-announce/2024040223-CVE-2024-26663-9705@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit ef20cd4 ("tipc: introduce UDP replicast") in v4.9-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc4.

Fixed status
mainline: [3871aa01e1a779d866fa9dfdd5a836f342f4eb87]
stable/4.19: [24ec8f0da93b8a9fba11600be8a90f0d73fb46f1]
stable/5.10: [19d7314f2fb9515bdaac9829d4d8eb34edd1fe95]
stable/5.15: [c1701ea85ef0ec7be6a1b36c7da69f572ed2fd12]
stable/5.4: [6f70f0b412458c622a12d4292782c8e92e210c2f]
stable/6.1: [3d3a5b31b43515b5752ff282702ca546ec3e48b6]
stable/6.6: [888e3524be87f3df9fa3c083484e4b62b3e3bb59]
stable/6.7: [0cd331dfd6023640c9669d0592bc0fd491205f87]

CVE-2024-26664: hwmon: (coretemp) Fix out-of-bounds memory access

Announce: https://lore.kernel.org/linux-cve-announce/2024040223-CVE-2024-26664-03db@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 7108b80 ("hwmon/coretemp: Handle large core ID
value") in v6.1-rc2.
This commit was backported to 4.19, 5.4, 5.10, and 5.15.
Fixed in v6.8-rc4.

Fixed status
mainline: [4e440abc894585a34c2904a32cd54af1742311b3]
stable/4.19: [93f0f4e846fcb682c3ec436e3b2e30e5a3a8ee6a]
stable/5.10: [f0da068c75c20ffc5ba28243ff577531dc2af1fd]
stable/5.15: [a16afec8e83c56b14a4a73d2e3fb8eec3a8a057e]
stable/5.4: [1eb74c00c9c3b13cb65e508c5d5a2f11afb96b8b]
stable/6.1: [9bce69419271eb8b2b3ab467387cb59c99d80deb]
stable/6.6: [853a6503c586a71abf27e60a7f8c4fb28092976d]
stable/6.7: [3a7753bda55985dc26fae17795cb10d825453ad1]

CVE-2024-26665: tunnels: fix out of bounds access when building IPv6 PMTU error

Announce: https://lore.kernel.org/linux-cve-announce/2024040224-CVE-2024-26665-5daa@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 4cb47a8 ("tunnels: PMTU discovery support for
directly bridged IP packets") in v5.9-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc4.

Fixed status
mainline: [d75abeec401f8c86b470e7028a13fcdc87e5dd06]
stable/5.10: [e77bf828f1ca1c47fcff58bdc26b60a9d3dfbe1d]
stable/5.15: [d964dd1bc1452594b4207d9229c157d9386e5d8a]
stable/6.1: [e37cde7a5716466ff2a76f7f27f0a29b05b9a732]
stable/6.6: [510c869ffa4068c5f19ff4df51d1e2f3a30aaac1]
stable/6.7: [7dc9feb8b1705cf00de20563b6bc4831f4c99dab]

CVE-2024-26666: wifi: mac80211: fix RCU use in TDLS fast-xmit

Announce: https://lore.kernel.org/linux-cve-announce/2024040224-CVE-2024-26666-fcfe@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 8cc0726 ("wifi: mac80211: handle TDLS data frames
with MLO") in v6.5-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc4.

Fixed status
mainline: [9480adfe4e0f0319b9da04b44e4eebd5ad07e0cd]
stable/6.6: [fc3432ae8232ff4025e7c55012dd88db0e3d18eb]
stable/6.7: [c255c3b653c6e8b52ac658c305e2fece2825f7ad]

CVE-2024-26667: drm/msm/dpu: check for valid hw_pp in
dpu_encoder_helper_phys_cleanup

Announce: https://lore.kernel.org/linux-cve-announce/2024040224-CVE-2024-26667-cf72@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit ae4d721 ("drm/msm/dpu: add an API to reset the
encoder related hw blocks") in v5.19-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc4.

Fixed status
mainline: [7f3d03c48b1eb6bc45ab20ca98b8b11be25f9f52]
stable/6.1: [fb8bfc6ea3cd8c5ac3d35711d064e2f6646aec17]
stable/6.6: [79592a6e7bdc1d05460c95f891f5e5263a107af8]
stable/6.7: [eb4f56f3ff5799ca754ae6d811803a63fe25a4a2]

CVE-2024-26668: netfilter: nft_limit: reject configurations that cause
integer overflow

Announce: https://lore.kernel.org/linux-cve-announce/2024040235-CVE-2024-26668-636e@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit d2168e8 ("netfilter: nft_limit: add per-byte
limiting") in v4.3-rc1.
Fixed in v6.8-rc2.

Fixed status
mainline: [c9d9eb9c53d37cdebbad56b91e40baf42d5a97aa]
stable/5.15: [79d4efd75e7dbecd855a3b8a63e65f7265f466e1]
stable/6.1: [bc6e242bb74e2ae616bfd2b250682b738e781c9b]
stable/6.6: [9882495d02ecc490604f747437a40626dc9160d0]
stable/6.7: [00c2c29aa36d1d1827c51a3720e9f893a22c7c6a]

CVE-2024-26669: net/sched: flower: Fix chain template offload

Announce: https://lore.kernel.org/linux-cve-announce/2024040237-CVE-2024-26669-ca3c@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit bbf7383 ("net: sched: traverse chains in block
with tcf_get_next_chain()") in v5.1-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc2.

Fixed status
mainline: [32f2a0afa95fae0d1ceec2ff06e0e816939964b8]
stable/6.6: [9ed46144cff3598a5cf79955630e795ff9af5b97]
stable/6.7: [c04709b2cc99ae31c346f79f0211752d7b74df01]

CVE-2024-26670: arm64: entry: fix ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD

Announce: https://lore.kernel.org/linux-cve-announce/2024040238-CVE-2024-26670-ecbd@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 471470b ("arm64: errata: Add Cortex-A520
speculative unprivileged load workaround") in v6.6-rc5.
This commit was backported to 6.1.
Fixed in v6.8-rc1.

Fixed status
mainline: [832dd634bd1b4e3bbe9f10b9c9ba5db6f6f2b97f]
stable/6.6: [58eb5c07f41704464b9acc09ab0707b6769db6c0]
stable/6.7: [baa0aaac16432019651e0d60c41cd34a0c3c3477]

CVE-2024-26671: blk-mq: fix IO hang from sbitmap wakeup race

Announce: https://lore.kernel.org/linux-cve-announce/2024040219-CVE-2024-26671-2543@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc1.
The blk_mq_mark_tag_wait() was renamed from blk_mq_dispatch_wait_add()
by commit f906a6a0f ("blk-mq: improve tag waiting setup for non-shared
tags")
in 4.15-rc1. The blk_mq_dispatch_wait_add() was introduced by commit
da55f2cc ("blk-mq: use sbq wait queues instead of restart for driver
tags") in 4.11-rc1.
So, Linux 4.4 may not be affected.

Fixed status
mainline: [5266caaf5660529e3da53004b8b7174cab6374ed]
stable/4.19: [9525b38180e2753f0daa1a522b7767a2aa969676]
stable/5.10: [7610ba1319253225a9ba8a9d28d472fc883b4e2f]
stable/5.15: [89e0e66682e1538aeeaa3109503473663cd24c8b]
stable/5.4: [ecd7744a1446eb02ccc63e493e2eb6ede4ef1e10]
stable/6.1: [1d9c777d3e70bdc57dddf7a14a80059d65919e56]
stable/6.6: [6d8b01624a2540336a32be91f25187a433af53a0]
stable/6.7: [f1bc0d8163f8ee84a8d5affdf624cfad657df1d2]

CVE-2024-26672: drm/amdgpu: Fix variable 'mca_funcs' dereferenced
before NULL check in 'amdgpu_mca_smu_get_mca_entry()'

Announce: https://lore.kernel.org/linux-cve-announce/2024040219-CVE-2024-26672-e96e@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc1.

Fixed status
mainline: [4f32504a2f85a7b40fe149436881381f48e9c0c0]
stable/6.7: [7b5d58c07024516c0e81b95e98f37710cf402c53]

CVE-2024-26673: netfilter: nft_ct: sanitize layer 3 and 4 protocol
number in custom expectations

Announce: https://lore.kernel.org/linux-cve-announce/2024040212-CVE-2024-26673-b2d3@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 857b460 ("netfilter: nft_ct: add ct expectations
support") in v5.3-rc1.
It looks as if commit 7ff607e2 ("drm/amdgpu: add amdgpu smu mca dump
feature support") in 6.7-rc1 introduced by this bug.
Fixed in v6.8-rc3.

Fixed status
mainline: [8059918a1377f2f1fff06af4f5a4ed3d5acd6bc4]
stable/5.10: [65ee90efc928410c6f73b3d2e0afdd762652c09d]
stable/5.15: [b775ced05489f4b77a35fe203e9aeb22f428e38f]
stable/5.4: [f549f340c91f08b938d60266e792ff7748dae483]
stable/6.1: [0f501dae16b7099e69ee9b0d5c70b8f40fd30e98]
stable/6.6: [cfe3550ea5df292c9e2d608e8c4560032391847e]
stable/6.7: [38cc1605338d99205a263707f4dde76408d3e0e8]

CVE-2024-26674: x86/lib: Revert to _ASM_EXTABLE_UA() for {get,put}_user() fixups

Announce: https://lore.kernel.org/linux-cve-announce/2024040252-CVE-2024-26674-4ff9@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit b19b74b ("x86/mm: Rework address range check in
get_user() and put_user()") in v6.4-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc4.

Fixed status
mainline: [8eed4e00a370b37b4e5985ed983dccedd555ea9d]
stable/6.6: [2aed1b6c33afd8599d01c6532bbecb829480a674]
stable/6.7: [2da241c5ed78d0978228a1150735539fe1a60eca]

CVE-2024-26675: ppp_async: limit MRU to 64K

Announce: https://lore.kernel.org/linux-cve-announce/2024040252-CVE-2024-26675-5b19@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 1da177e ("Linux-2.6.12-rc2") in v2.6.12.
Fixed in v6.8-rc4.

Fixed status
cip/4.4: [37a53d8baa59dffb752a1dd9e85888090fd05c7e]
cip/4.4-rt: [37a53d8baa59dffb752a1dd9e85888090fd05c7e]
cip/4.4-st: [37a53d8baa59dffb752a1dd9e85888090fd05c7e]
mainline: [cb88cb53badb8aeb3955ad6ce80b07b598e310b8]
stable/4.19: [4fdb14ba89faff6e6969a4dffdc8e54235d6e5ed]
stable/5.10: [b06e067e93fa4b98acfd3a9f38a398ab91bbc58b]
stable/5.15: [58fbe665b097bf7b3144da7e7b91fb27aa8d0ae3]
stable/5.4: [56fae81633ccee307cfcb032f706bf1863a56982]
stable/6.1: [4e2c4846b2507f6dfc9bea72b7567c2693a82a16]
stable/6.6: [7e5ef49670766c9742ffcd9cead7cdb018268719]
stable/6.7: [210d938f963dddc543b07e66a79b7d8d4bd00bd8]

CVE-2024-26676: af_unix: Call kfree_skb() for dead unix_(sk)->oob_skb in GC.

Announce: https://lore.kernel.org/linux-cve-announce/2024040252-CVE-2024-26676-222f@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 2aab4b9 ("af_unix: fix struct pid leaks in OOB
support") in v6.3-rc2.
This commit was backported to 6.1 and 5.15.
Fixed in v6.8-rc4.

Fixed status
mainline: [1279f9d9dec2d7462823a18c29ad61359e0a007d]
stable/5.15: [4fe505c63aa3273135a57597fda761e9aecc7668]
stable/6.1: [e0e09186d8821ad59806115d347ea32efa43ca4b]
stable/6.6: [b74aa9ce13d02b7fd37c5325b99854f91b9b4276]
stable/6.7: [82ae47c5c3a6b27fdc0f9e83c1499cb439c56140]

CVE-2024-26677: rxrpc: Fix delayed ACKs to not set the reference serial number

Announce: https://lore.kernel.org/linux-cve-announce/2024040252-CVE-2024-26677-8bc6@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 17926a7 ("[AF_RXRPC]: Provide secure RxRPC
sockets for use by userspace and kernel both") in v2.6.22-rc1.
Fixed in v6.8-rc4.

Fixed status
mainline: [e7870cf13d20f56bfc19f9c3e89707c69cf104ef]
stable/6.6: [200cb50b9e154434470c8969d32474d38475acc2]
stable/6.7: [63719f490e6a89896e9a463d2b45e8203eab23ae]

CVE-2024-26678: x86/efistub: Use 1:1 file:memory mapping for PE/COFF
.compat section

Announce: https://lore.kernel.org/linux-cve-announce/2024040253-CVE-2024-26678-2cf0@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 3e3eabe ("x86/boot: Increase section and file
alignment to 4k/512") in v6.7-rc1.
This commit was backported to 6.6.
Fixed in v6.8-rc4.

Fixed status
mainline: [1ad55cecf22f05f1c884adf63cc09d3c3e609ebf]
stable/6.6: [0a962f2fbaa976af9eed21d0306370cded485787]
stable/6.7: [4adeeff8c12321cd453412a659c3c0eeb9bb2397]

CVE-2024-26679: inet: read sk->sk_family once in inet_recv_error()

Announce: https://lore.kernel.org/linux-cve-announce/2024040253-CVE-2024-26679-d520@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit f4713a3 ("net-timestamp: make tcp_recvmsg call
ipv6_recv_error for AF_INET6 socks") in v3.18-rc7.
Fixed in v6.8-rc4.

Fixed status
cip/4.4: [bb8d857ec2d255cdba76631c733f8d722b5ab6bc]
cip/4.4-rt: [bb8d857ec2d255cdba76631c733f8d722b5ab6bc]
cip/4.4-st: [bb8d857ec2d255cdba76631c733f8d722b5ab6bc]
mainline: [eef00a82c568944f113f2de738156ac591bbd5cd]
stable/4.19: [caa064c3c2394d03e289ebd6b0be5102eb8a5b40]
stable/5.10: [88081ba415224cf413101def4343d660f56d082b]
stable/5.15: [3266e638ba5cc1165f5e6989eb8c0720f1cc4b41]
stable/5.4: [5993f121fbc01dc2d734f0ff2628009b258fb1dd]
stable/6.1: [54538752216bf89ee88d47ad07802063a498c299]
stable/6.6: [4a5e31bdd3c1702b520506d9cf8c41085f75c7f2]
stable/6.7: [307fa8a75ab7423fa5c73573ec3d192de5027830]

CVE-2024-26680: net: atlantic: Fix DMA mapping for PTP hwts ring

Announce: https://lore.kernel.org/linux-cve-announce/2024040253-CVE-2024-26680-d16c@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 94ad945 ("net: aquantia: add PTP rings
infrastructure") in v5.5-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc4.

Fixed status
mainline: [2e7d3b67630dfd8f178c41fa2217aa00e79a5887]
stable/6.1: [466ceebe48cbba3f4506f165fca7111f9eb8bb12]
stable/6.6: [004fe5b7f59286a926a45e0cafc7870e9cdddd56]
stable/6.7: [e42e334c645575be5432adee224975d4f536fdb1]

CVE-2024-26681: netdevsim: avoid potential loop in nsim_dev_trap_report_work()

Announce: https://lore.kernel.org/linux-cve-announce/2024040253-CVE-2024-26681-7e46@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 012ec02 ("netdevsim: convert driver to use
unlocked devlink API during init/fini") in v6.0-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc4.

Fixed status
mainline: [ba5e1272142d051dcc57ca1d3225ad8a089f9858]
stable/6.1: [0193e0660cc6689c794794b471492923cfd7bfbc]
stable/6.6: [6eecddd9c3c8d6e3a097531cdc6d500335b35e46]
stable/6.7: [d91964cdada76740811b7c621239f9c407820dbc]

CVE-2024-26682: wifi: mac80211: improve CSA/ECSA connection refusal

Announce: https://lore.kernel.org/linux-cve-announce/2024040254-CVE-2024-26682-f2b2@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit c09c4f3 ("wifi: mac80211: don't connect to an AP
while it's in a CSA process") in v6.7-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc4.

Fixed status
mainline: [35e2385dbe787936c793d70755a5177d267a40aa]
stable/6.7: [ea88bde8e3fefbe4268f6991375dd629895a090a]

CVE-2024-26683: wifi: cfg80211: detect stuck ECSA element in probe resp

Announce: https://lore.kernel.org/linux-cve-announce/2024040254-CVE-2024-26683-8614@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit c09c4f3 ("wifi: mac80211: don't connect to an AP
while it's in a CSA process") in v6.7-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc4.

Fixed status
mainline: [177fbbcb4ed6b306c1626a277fac3fb1c495a4c7]
stable/6.7: [ce112c941c2b172afba3e913a90c380647d53975]

CVE-2024-26684: net: stmmac: xgmac: fix handling of DPP safety error
for DMA channels

Announce: https://lore.kernel.org/linux-cve-announce/2024040254-CVE-2024-26684-7ce8@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 56e58d6 ("net: stmmac: Implement Safety Features
in XGMAC core") in v5.4-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc4.

Fixed status
mainline: [46eba193d04f8bd717e525eb4110f3c46c12aec3]
stable/5.10: [2fc45a4631ac7837a5c497cb4f7e2115d950fc37]
stable/5.15: [6609e98ed82966a1b3168c142aca30f8284a7b89]
stable/5.4: [e9837c83befb5b852fa76425dde98a87b737df00]
stable/6.1: [e42ff0844fe418c7d03a14f9f90e1b91ba119591]
stable/6.6: [7e0ff50131e9d1aa507be8e670d38e9300a5f5bf]
stable/6.7: [3b48c9e258c8691c2f093ee07b1ea3764caaa1b2]

CVE-2023-52637: can: j1939: Fix UAF in j1939_sk_match_filter during
setsockopt(SO_J1939_FILTER)

Announce: https://lore.kernel.org/linux-cve-announce/2024040332-CVE-2023-52637-5e37@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 9d71dd0 ("can: add support of SAE J1939
protocol") in v5.4-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc5.

Fixed status
mainline: [efe7cf828039aedb297c1f9920b638fffee6aabc]
stable/5.10: [978e50ef8c38dc71bd14d1b0143d554ff5d188ba]
stable/5.15: [41ccb5bcbf03f02d820bc6ea8390811859f558f8]
stable/5.4: [08de58abedf6e69396e1207e4f99ef8904b2b532]
stable/6.1: [4dd684d4bb3cd5454e0bf6e2a1bdfbd5c9c872ed]
stable/6.6: [f84e7534457dcd7835be743517c35378bb4e7c50]
stable/6.7: [fc74b9cb789cae061bbca7b203a3842e059f6b5d]

CVE-2023-52638: can: j1939: prevent deadlock by changing
j1939_socks_lock to rwlock

Announce: https://lore.kernel.org/linux-cve-announce/2024040334-CVE-2023-52638-26a6@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc5.
The can/j1939 was introduced by commit ("can: add support of SAE J1939
protocol") in 5.4-rc1. It looks like this bug was introduced by the
commit.

Fixed status
mainline: [6cdedc18ba7b9dacc36466e27e3267d201948c8d]
stable/5.15: [03358aba991668d3bb2c65b3c82aa32c36851170]
stable/6.1: [aedda066d717a0b4335d7e0a00b2e3a61e40afcf]
stable/6.6: [26dfe112ec2e95fe0099681f6aec33da13c2dd8e]
stable/6.7: [559b6322f9480bff68cfa98d108991e945a4f284]

CVE-2023-52639: KVM: s390: vsie: fix race during shadow creation

Announce: https://lore.kernel.org/linux-cve-announce/2024040335-CVE-2023-52639-5b67@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit a3508fb ("KVM: s390: vsie: initial support for
nested virtualization") in v4.8-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc4.

Fixed status
mainline: [fe752331d4b361d43cfd0b89534b4b2176057c32]
stable/6.1: [5df3b81a567eb565029563f26f374ae3803a1dfc]
stable/6.6: [f5572c0323cf8b4f1f0618178648a25b8fb8a380]
stable/6.7: [28bb27824f25f36e5f80229a358d66ee09244082]

CVE-2023-52640: fs/ntfs3: Fix oob in ntfs_listxattr

Announce: https://lore.kernel.org/linux-cve-announce/2024040355-CVE-2023-52640-2657@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc4.
The ntfs3's attribute operation was introduced by commit be71b5cba
("fs/ntfs3: Add attrib operations") in 5.15-rc1.
So, prior to Linux 5.15 is not affected.

Fixed status
mainline: [731ab1f9828800df871c5a7ab9ffe965317d3f15]
stable/5.15: [a585faf0591548fe0920641950ebfa8a6eefe1cd]
stable/6.1: [6ed6cdbe88334ca3430c5aee7754dc4597498dfb]
stable/6.6: [52fff5799e3d1b5803ecd2f5f19c13c65f4f7b23]
stable/6.7: [0830c5cf19bdec50d0ede4755ddc463663deb21c]

CVE-2023-52641: fs/ntfs3: Add NULL ptr dereference checking at the end
of attr_allocate_frame()

Announce: https://lore.kernel.org/linux-cve-announce/2024040357-CVE-2023-52641-1c18@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc4.
The ntfs3's arrtib operations was introduced by commit be71b5cb
("fs/ntfs3: Add attrib operations") in 5.15-rc1.
This commit introduced this bug.

Fixed status
mainline: [aaab47f204aaf47838241d57bf8662c8840de60a]
stable/5.15: [ee8db6475cb15c8122855f72ad4cfa5375af6a7b]
stable/6.1: [50545eb6cd5f7ff852a01fa29b7372524ef948cc]
stable/6.6: [947c3f3d31ea185ddc8e7f198873f17d36deb24c]
stable/6.7: [847b68f58c212f0439c5a8101b3841f32caffccd]

CVE-2024-26685: nilfs2: fix potential bug in end_buffer_async_write

Announce: https://lore.kernel.org/linux-cve-announce/2024040335-CVE-2024-26685-e15e@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 7f42ec3 ("nilfs2: fix issue with race condition
of competition between segments for dirty blocks") in v3.12-rc4.
Fixed in v6.8-rc4.

Fixed status
cip/4.4: [ac338f456db88bd4c653e01151074320959ac404]
cip/4.4-rt: [ac338f456db88bd4c653e01151074320959ac404]
cip/4.4-st: [ac338f456db88bd4c653e01151074320959ac404]
mainline: [5bc09b397cbf1221f8a8aacb1152650c9195b02b]
stable/4.19: [c4a09fdac625e64abe478dcf88bfa20406616928]
stable/5.10: [f3e4963566f58726d3265a727116a42b591f6596]
stable/5.15: [8fa90634ec3e9cc50f42dd605eec60f2d146ced8]
stable/5.4: [d31c8721e816eff5ca6573cc487754f357c093cd]
stable/6.1: [6589f0f72f8edd1fa11adce4eedbd3615f2e78ab]
stable/6.6: [2c3bdba00283a6c7a5b19481a59a730f46063803]
stable/6.7: [626daab3811b772086aef1bf8eed3ffe6f523eff]

CVE-2024-26686: fs/proc: do_task_stat: use sig->stats_lock to gather
the threads/children stats

Announce: https://lore.kernel.org/linux-cve-announce/2024040335-CVE-2024-26686-b22f@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc4.
It may affect all stable kernels.

Fixed status
mainline: [7601df8031fd67310af891897ef6cc0df4209305]
stable/6.1: [cf4b8c39b9a0bd81c47afc7ef62914a62dd5ec4d]
stable/6.7: [27978243f165b44e342f28f449b91327944ea071]

CVE-2024-26687: xen/events: close evtchn after mapping cleanup

Announce: https://lore.kernel.org/linux-cve-announce/2024040335-CVE-2024-26687-55d0@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit d46a78b ("xen: implement pirq type event
channels") in v2.6.37-rc1.
Backporting to this fix to 4.19
(https://lore.kernel.org/stable/2024021921-why-roamer-871c@gregkh/),
5.10 (https://lore.kernel.org/stable/2024021914-wackiness-diagnoses-52e2@gregkh/),
5.15 (https://lore.kernel.org/stable/2024021911-king-sugar-1024@gregkh/), and
5.4 (https://lore.kernel.org/stable/2024021917-krypton-upcountry-d467@gregkh/)
were failed.
Fixed in v6.8-rc5.

Fixed status
mainline: [fa765c4b4aed2d64266b694520ecb025c862c5a9]
stable/6.1: [585a344af6bcac222608a158fc2830ff02712af5]
stable/6.6: [20980195ec8d2e41653800c45c8c367fa1b1f2b4]
stable/6.7: [9be71aa12afa91dfe457b3fb4a444c42b1ee036b]

CVE-2024-26688: fs,hugetlb: fix NULL pointer dereference in hugetlbs_fill_super

Announce: https://lore.kernel.org/linux-cve-announce/2024040336-CVE-2024-26688-7b0e@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 3202198 ("hugetlbfs: Convert to fs_context") in v5.1-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc4.

Fixed status
mainline: [79d72c68c58784a3e1cd2378669d51bfd0cb7498]
stable/5.10: [80d852299987a8037be145a94f41874228f1a773]
stable/5.15: [22850c9950a4e43a67299755d11498f3292d02ff]
stable/5.4: [1dde8ef4b7a749ae1bc73617c91775631d167557]
stable/6.1: [2e2c07104b4904aed1389a59b25799b95a85b5b9]
stable/6.6: [13c5a9fb07105557a1fa9efdb4f23d7ef30b7274]
stable/6.7: [ec78418801ef7b0c22cd6a30145ec480dd48db39]

CVE-2024-26689: ceph: prevent use-after-free in encode_cap_msg()

Announce: https://lore.kernel.org/linux-cve-announce/2024040336-CVE-2024-26689-990b@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc4.
Commit 0a454bdd ("ceph: reorganize __send_cap for less spinlock
abuse") in 5.8-rc1 introduced the __prep_cap().
It seems as if this commit introduced this bug.

Fixed status
mainline: [cda4672da1c26835dcbd7aec2bfed954eda9b5ef]
stable/5.10: [8180d0c27b93a6eb60da1b08ea079e3926328214]
stable/5.15: [70e329b440762390258a6fe8c0de93c9fdd56c77]
stable/6.1: [f3f98d7d84b31828004545e29fd7262b9f444139]
stable/6.6: [ae20db45e482303a20e56f2db667a9d9c54ac7e7]
stable/6.7: [7958c1bf5b03c6f1f58e724dbdec93f8f60b96fc]

CVE-2024-26690: net: stmmac: protect updates of 64-bit statistics counters

Announce: https://lore.kernel.org/linux-cve-announce/2024040336-CVE-2024-26690-0097@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 133466c ("net: stmmac: use per-queue 64 bit
statistics where necessary") in v6.6-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc4.

Fixed status
mainline: [38cc3c6dcc09dc3a1800b5ec22aef643ca11eab8]
stable/6.6: [9680b2ab54ba8d72581100e8c45471306101836e]
stable/6.7: [e6af0f082a4b87b99ad033003be2a904a1791b3f]

CVE-2024-26691: KVM: arm64: Fix circular locking dependency

Announce: https://lore.kernel.org/linux-cve-announce/2024040336-CVE-2024-26691-fff7@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc5.
Vulnerable functions were introduced by commit 9d0c063 ("KVM: arm64:
Instantiate pKVM hypervisor VM and vCPU structures from EL1") in
6.2-rc1.

Fixed status
mainline: [10c02aad111df02088d1a81792a709f6a7eca6cc]
stable/6.6: [3d16cebf01127f459dcfeb79ed77bd68b124c228]
stable/6.7: [3ab1c40a1e915e350d9181a4603af393141970cc]

CVE-2024-26692: smb: Fix regression in writes when non-standard
maximum write size negotiated

Announce: https://lore.kernel.org/linux-cve-announce/2024040337-CVE-2024-26692-162f@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit d08089f ("cifs: Change the I/O paths to use an
iterator rather than a page list") in v6.3-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc5.

Fixed status
mainline: [4860abb91f3d7fbaf8147d54782149bb1fc45892]
stable/6.6: [4145ccff546ea868428b3e0fe6818c6261b574a9]
stable/6.7: [63c35afd50e28b49c5b75542045a8c42b696dab9]

CVE-2024-26693: wifi: iwlwifi: mvm: fix a crash when we run out of stations

Announce: https://lore.kernel.org/linux-cve-announce/2024040337-CVE-2024-26693-9c3b@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 57974a5 ("wifi: iwlwifi: mvm: refactor
iwl_mvm_mac_sta_state_common()") in v6.4-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc5.

Fixed status
mainline: [b7198383ef2debe748118996f627452281cf27d7]
stable/6.6: [00f4eb31b8193f6070ce24df636883f9c104ca95]
stable/6.7: [c12f0f4d4caf23b1bfdc2602b6b70d56bdcd6aa7]

CVE-2024-26694: wifi: iwlwifi: fix double-free bug

Announce: https://lore.kernel.org/linux-cve-announce/2024040337-CVE-2024-26694-b216@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 5e31b3d ("wifi: iwlwifi: dbg: print pc register
data once fw dump occurred") in v6.4-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc4.

Fixed status
mainline: [353d321f63f7dbfc9ef58498cc732c9fe886a596]
stable/6.6: [ab9d4bb9a1892439b3123fc52b19e32b9cdf80ad]
stable/6.7: [d24eb9a27bea8fe5237fa71be274391d9d51eff2]

CVE-2024-26695: crypto: ccp - Fix null pointer dereference in
__sev_platform_shutdown_locked

Announce: https://lore.kernel.org/linux-cve-announce/2024040338-CVE-2024-26695-e41f@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 1b05ece ("crypto: ccp - During shutdown, check
SEV data pointer before using") in v6.0-rc1.
This commit was backported to 5.10 and 5.15.
Fixed in v6.8-rc4.

Fixed status
mainline: [ccb88e9549e7cfd8bcd511c538f437e20026e983]
stable/5.10: [58054faf3bd29cd0b949b77efcb6157f66f401ed]
stable/5.15: [7535ec350a5f09b5756a7607f5582913f21200f4]
stable/6.1: [8731fe001a60581794ed9cf65da8cd304846a6fb]
stable/6.6: [88aa493f393d2ee38ac140e1f6ac1881346e85d4]
stable/6.7: [b5909f197f3b26aebedca7d8ac7b688fd993a266]

CVE-2024-26696: nilfs2: fix hang in nilfs_lookup_dirty_data_buffers()

Announce: https://lore.kernel.org/linux-cve-announce/2024040338-CVE-2024-26696-9dff@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 1d1d1a7 ("mm: only enforce stable page writes if
the backing device requires it") in v3.9-rc1.
Fixed in v6.8-rc4.

Fixed status
cip/4.4: [61870bf424a21fe93d918909c6e7148f85f51278]
cip/4.4-rt: [61870bf424a21fe93d918909c6e7148f85f51278]
cip/4.4-st: [61870bf424a21fe93d918909c6e7148f85f51278]
mainline: [38296afe3c6ee07319e01bb249aa4bb47c07b534]
stable/4.19: [228742b2ddfb99dfd71e5a307e6088ab6836272e]
stable/5.10: [98a4026b22ff440c7f47056481bcbbe442f607d6]
stable/5.15: [7e9b622bd0748cc104d66535b76d9b3535f9dc0f]
stable/5.4: [862ee4422c38be5c249844a684b00d0dbe9d1e46]
stable/6.1: [8494ba2c9ea00a54d5b50e69b22c55a8958bce32]
stable/6.6: [ea5ddbc11613b55e5128c85f57b08f907abd9b28]
stable/6.7: [e38585401d464578d30f5868ff4ca54475c34f7d]

CVE-2024-26697: nilfs2: fix data corruption in dsync block recovery
for small block sizes

Announce: https://lore.kernel.org/linux-cve-announce/2024040338-CVE-2024-26697-9521@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc4.

Fixed status
cip/4.4: [3cd3a103704de7170df4b51e063c61e95fc14962]
cip/4.4-rt: [3cd3a103704de7170df4b51e063c61e95fc14962]
cip/4.4-st: [3cd3a103704de7170df4b51e063c61e95fc14962]
mainline: [67b8bcbaed4777871bb0dcc888fb02a614a98ab1]
stable/4.19: [5278c3eb6bf5896417572b52adb6be9d26e92f65]
stable/5.10: [364a66be2abdcd4fd426ffa44d9b8f40aafb3caa]
stable/5.15: [120f7fa2008e3bd8b7680b4ab5df942decf60fd5]
stable/5.4: [a6efe6dbaaf504f5b3f8a5c3f711fe54e7dda0ba]
stable/6.1: [9c9c68d64fd3284f7097ed6ae057c8441f39fcd3]
stable/6.6: [2e1480538ef60bfee5473dfe02b1ecbaf1a4aa0d]
stable/6.7: [2000016bab499074e6248ea85aeea7dd762355d9]

CVE-2024-26698: hv_netvsc: Fix race condition between netvsc_probe and
netvsc_remove

Announce: https://lore.kernel.org/linux-cve-announce/2024040338-CVE-2024-26698-36ac@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit ac50476 ("hv_netvsc: Disable NAPI before closing
the VMBus channel") in v5.8-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc3.

Fixed status
mainline: [e0526ec5360a48ad3ab2e26e802b0532302a7e11]
stable/5.10: [9ec807e7b6f5fcf9499f3baa69f254bb239a847f]
stable/5.15: [7656372ae190e54e8c8cf1039725a5ea59fdf84a]
stable/6.1: [48a8ccccffbae10c91d31fc872db5c31aba07518]
stable/6.6: [22a77c0f5b8233237731df3288d067af51a2fd7b]
stable/6.7: [0e8875de9dad12805ff66e92cd5edea6a421f1cd]

CVE-2024-26699: drm/amd/display: Fix array-index-out-of-bounds in dcn35_clkmgr

Announce: https://lore.kernel.org/linux-cve-announce/2024040339-CVE-2024-26699-c700@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc5.
Affected file drivers/gpu/drm/amd/display/dc/clk_mgr/dcn35/dcn35_clk_mgr.c
was introduced by commit in 8774029f ("drm/amd/display: Add DCN35
CLK_MGR") in 6.7-rc1.

Fixed status
mainline: [46806e59a87790760870d216f54951a5b4d545bc]
stable/6.7: [ca400d8e0c1c9d79c08dfb6b7f966e26c8cae7fb]

CVE-2024-26700: drm/amd/display: Fix MST Null Ptr for RV

Announce: https://lore.kernel.org/linux-cve-announce/2024040339-CVE-2024-26700-a2b8@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc4.
The compute_mst_dsc_configs_for_state() was introduced by commit
8c20a1e ("drm/amd/display: MST DSC compute fair share") in 5.6-rc1.
It seems as if 5.10 and 5.15 are affected.

Fixed status
mainline: [e6a7df96facdcf5b1f71eb3ec26f2f9f6ad61e57]
stable/6.1: [01d992088dce3945f70f49f34b0b911c5213c238]
stable/6.6: [7407c61f43b66e90ad127d0cdd13cbc9d87141a5]
stable/6.7: [5cd7185d2db76c42a9b7e69adad9591d9fca093f]

CVE-2024-26702: iio: magnetometer: rm3100: add boundary check for the
value read from RM3100_REG_TMRC

Announce: https://lore.kernel.org/linux-cve-announce/2024040339-CVE-2024-26702-acda@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 121354b ("iio: magnetometer: Add driver support
for PNI RM3100") in v5.0-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc5.

Fixed status
mainline: [792595bab4925aa06532a14dd256db523eb4fa5e]
stable/5.10: [36a49290d7e6d554020057a409747a092b1d3b56]
stable/5.15: [8d5838a473e8e6d812257c69745f5920e4924a60]
stable/5.4: [7200170e88e3ec54d9e9c63f07514c3cead11481]
stable/6.1: [176256ff8abff29335ecff905a09fb49e8dcf513]
stable/6.6: [1d8c67e94e9e977603473a543d4f322cf2c4aa01]
stable/6.7: [57d05dbbcd0b3dc0c252103b43012eef5d6430d1]

CVE-2024-26703: tracing/timerlat: Move hrtimer_init to timerlat_fd open()

Announce: https://lore.kernel.org/linux-cve-announce/2024040340-CVE-2024-26703-d60d@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit e88ed22 ("tracing/timerlat: Add user-space
interface") in v6.5-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc3.

Fixed status
mainline: [1389358bb008e7625942846e9f03554319b7fecc]
stable/6.6: [5f703935fdb559642d85b2088442ee55a557ae6d]
stable/6.7: [2354d29986ebd138f89c2b73fecf8237e0a4ad6b]

CVE-2024-26704: ext4: fix double-free of blocks due to wrong extents moved_len

Announce: https://lore.kernel.org/linux-cve-announce/2024040340-CVE-2024-26704-a082@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit fcf6b1b ("ext4: refactor ext4_move_extents code
base") in v3.18-rc2.
Fixed in v6.8-rc3.

Fixed status
cip/4.4: [052905e830d7a5f7bf023f09a028cc7546b38339]
cip/4.4-rt: [052905e830d7a5f7bf023f09a028cc7546b38339]
cip/4.4-st: [052905e830d7a5f7bf023f09a028cc7546b38339]
mainline: [55583e899a5357308274601364741a83e78d6ac4]
stable/4.19: [b4fbb89d722cbb16beaaea234b7230faaaf68c71]
stable/5.10: [d033a555d9a1cf53dbf3301af7199cc4a4c8f537]
stable/5.15: [afba9d11320dad5ce222ac8964caf64b7b4bedb1]
stable/5.4: [afbcad9ae7d6d11608399188f03a837451b6b3a1]
stable/6.1: [185eab30486ba3e7bf8b9c2e049c79a06ffd2bc1]
stable/6.6: [2883940b19c38d5884c8626483811acf4d7e148f]
stable/6.7: [559ddacb90da1d8786dd8ec4fd76bbfa404eaef6]

CVE-2024-26705: parisc: BTLB: Fix crash when setting up BTLB at CPU bringup

Announce: https://lore.kernel.org/linux-cve-announce/2024040340-CVE-2024-26705-c0ff@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit e5ef93d ("parisc: BTLB: Initialize BTLB tables at
CPU startup") in v6.6-rc2.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc3.

Fixed status
mainline: [913b9d443a0180cf0de3548f1ab3149378998486]
stable/6.6: [54944f45470af5965fb9c28cf962ec30f38a8f5b]
stable/6.7: [aa52be55276614d33f22fbe7da36c40d6432d10b]

CVE-2024-26706: parisc: Fix random data corruption from exception handler

Announce: https://lore.kernel.org/linux-cve-announce/2024040341-CVE-2024-26706-844b@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc3.
Since commit 4b9d2a731 ("parisc: Switch user access functions to
signal errors in r29 instead of r8") in 5.17-rc1,
use register r29 instead of register r8 to signal faults when
accessing user memory.
So, before 5.17 may not be affected.

Fixed status
mainline: [8b1d72395635af45410b66cc4c4ab37a12c4a831]
stable/6.1: [23027309b099ffc4efca5477009a11dccbdae592]
stable/6.6: [fa69a8063f8b27f3c7434a0d4f464a76a62f24d2]
stable/6.7: [ce31d79aa1f13a2345791f84935281a2c194e003]

CVE-2024-26707: net: hsr: remove WARN_ONCE() in send_hsr_supervision_frame()

Announce: https://lore.kernel.org/linux-cve-announce/2024040341-CVE-2024-26707-1153@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 121c33b ("net: hsr: introduce common code for skb
initialization") in v5.9-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc3.

Fixed status
mainline: [37e8c97e539015637cb920d3e6f1e404f707a06e]
stable/5.10: [0d8011a878fdf96123bc0d6a12e2fe7ced5fddfb]
stable/5.15: [de769423b2f053182a41317c4db5a927e90622a0]
stable/6.1: [56440799fc4621c279df16176f83a995d056023a]
stable/6.6: [923dea2a7ea9e1ef5ac4031fba461c1cc92e32b8]
stable/6.7: [547545e50c913861219947ce490c68a1776b9b51]

CVE-2024-26708: mptcp: really cope with fastopen race

Announce: https://lore.kernel.org/linux-cve-announce/2024040341-CVE-2024-26708-c98a@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 1e777f3 ("mptcp: add MSG_FASTOPEN sendmsg flag
support") in v6.2-rc1.
Introduced by commit 4fd19a3 ("mptcp: fix inconsistent state on
fastopen race") in v6.7-rc7.
These commits were backported to 6.6.
Fixed in v6.8-rc5.

Fixed status
mainline: [337cebbd850f94147cee05252778f8f78b8c337f]
stable/6.6: [4bfe217e075d04e63c092df9d40c608e598c2ef2]
stable/6.7: [e158fb9679d15a2317ec13b4f6301bd26265df2f]

CVE-2024-26709: powerpc/iommu: Fix the missing iommu_group_put()
during platform domain attach

Announce: https://lore.kernel.org/linux-cve-announce/2024040341-CVE-2024-26709-19b4@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit a8ca9fc ("powerpc/iommu: Do not do platform
domain attach atctions after probe") in v6.7-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc5.

Fixed status
mainline: [0846dd77c8349ec92ca0079c9c71d130f34cb192]
stable/6.7: [c90fdea9cac9eb419fc266e75d625cb60c8f7f6c]

CVE-2024-26710: powerpc/kasan: Limit KASAN thread size increase to 32KB

Announce: https://lore.kernel.org/linux-cve-announce/2024040342-CVE-2024-26710-6332@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 18f14afe2816 ("powerpc/64s: Increase default
stack  size to 32KB") in 6.8-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc5.

Fixed status
mainline: [f1acb109505d983779bbb7e20a1ee6244d2b5736]
stable/6.1: [4297217bcf1f0948a19c2bacc6b68d92e7778ad9]
stable/6.6: [4cc31fa07445879a13750cb061bb8c2654975fcb]
stable/6.7: [b29b16bd836a838b7690f80e37f8376414c74cbe]

CVE-2024-26711: iio: adc: ad4130: zero-initialize clock init data

Announce: https://lore.kernel.org/linux-cve-announce/2024040342-CVE-2024-26711-de47@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 6209406 ("iio: adc: ad4130: add AD4130 driver")
in v6.2-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc5.

Fixed status
mainline: [a22b0a2be69a36511cb5b37d948b651ddf7debf3]
stable/6.6: [0e0dab37750926d4fb0144edb1c1ea0612fea273]
stable/6.7: [02876e2df02f8b17a593d77a0a7879a8109b27e1]

CVE-2024-26712: powerpc/kasan: Fix addr error caused by page alignment

Announce: https://lore.kernel.org/linux-cve-announce/2024040342-CVE-2024-26712-d713@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 663c0c9 ("powerpc/kasan: Fix shadow area set up
for modules.") in v5.4-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc5.

Fixed status
mainline: [4a7aee96200ad281a5cc4cf5c7a2e2a49d2b97b0]
stable/5.10: [230e89b5ad0a33f530a2a976b3e5e4385cb27882]
stable/5.15: [2738e0aa2fb24a7ab9c878d912dc2b239738c6c6]
stable/6.1: [0c09912dd8387e228afcc5e34ac5d79b1e3a1058]
stable/6.6: [0516c06b19dc64807c10e01bb99b552bdf2d7dbe]
stable/6.7: [70ef2ba1f4286b2b73675aeb424b590c92d57b25]

CVE-2024-26713: powerpc/pseries/iommu: Fix iommu initialisation during DLPAR add

Announce: https://lore.kernel.org/linux-cve-announce/2024040342-CVE-2024-26713-1b52@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit a940904 ("powerpc/iommu: Add iommu_ops to report
capabilities and allow blocking domains") in v6.4-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc5.

Fixed status
mainline: [ed8b94f6e0acd652ce69bd69d678a0c769172df8]
stable/6.6: [9978d5b744e0227afe19e3bcb4c5f75442dde753]
stable/6.7: [d4f762d6403f7419de90d7749fa83dd92ffb0e1d]

CVE-2024-26714: interconnect: qcom: sc8180x: Mark CO0 BCM keepalive

Announce: https://lore.kernel.org/linux-cve-announce/2024040343-CVE-2024-26714-d9a8@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 9c8c6ba ("interconnect: qcom: Add SC8180x
providers") in v5.15-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc5.

Fixed status
mainline: [85e985a4f46e462a37f1875cb74ed380e7c0c2e0]
stable/6.1: [6616d3c4f8284a7b3ef978c916566bd240cea1c7]
stable/6.6: [d8e36ff40cf9dadb135f3a97341c02c9a7afcc43]
stable/6.7: [7a3a70dd08e4b7dffc2f86f2c68fc3812804b9d0]

CVE-2024-26715: usb: dwc3: gadget: Fix NULL pointer dereference in
dwc3_gadget_suspend

Announce: https://lore.kernel.org/linux-cve-announce/2024040343-CVE-2024-26715-20ed@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 9772b47 ("usb: dwc3: gadget: Fix suspend/resume
during device mode") in v4.6-rc5.
This commit was backported to 4.4 by commit df2ca3271.
Fixed in v6.8-rc3.
Backporting the fix to 4.19
(https://lore.kernel.org/stable/2024021815-crate-unsettled-85a8@gregkh/),
5.4 (https://lore.kernel.org/stable/2024021814-anointer-vanish-667b@gregkh/),
and
5.10 (https://lore.kernel.org/stable/2024021813-bubbling-outage-eadc@gregkh/)
were failed.

Fixed status
mainline: [61a348857e869432e6a920ad8ea9132e8d44c316]
stable/5.15: [88936ceab6b426f1312327e9ef849c215c6007a7]
stable/6.1: [57e2e42ccd3cd6183228269715ed032f44536751]
stable/6.6: [c7ebd8149ee519d27232e6e4940e9c02071b568b]
stable/6.7: [36695d5eeeefe5a64b47d0336e7c8fc144e78182]

CVE-2024-26716: usb: core: Prevent null pointer dereference in
update_port_device_state

Announce: https://lore.kernel.org/linux-cve-announce/2024040343-CVE-2024-26716-74a8@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 83cb260 ("usb: core: add sysfs entry for usb
device state") in v6.5-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc3.

Fixed status
mainline: [12783c0b9e2c7915a50d5ec829630ff2da50472c]
stable/6.6: [ed85777c640cf9e6920bb1b60ed8cd48e1f4d873]
stable/6.7: [465b545d1d7ef282192ddd4439b08279bdb13f6f]

CVE-2024-26717: HID: i2c-hid-of: fix NULL-deref on failed power up

Announce: https://lore.kernel.org/linux-cve-announce/2024040344-CVE-2024-26717-0d01@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit b33752c ("HID: i2c-hid: Reorganize so ACPI and OF
are separate modules") in v5.12-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc3.

Fixed status
mainline: [00aab7dcb2267f2aef59447602f34501efe1a07f]
stable/5.15: [62f5d219edbd174829aa18d4b3d97cd5fefbb783]
stable/6.1: [d7d7a0e3b6f5adc45f23667cbb919e99093a5b5c]
stable/6.6: [4cad91344a62536a2949873bad6365fbb6232776]
stable/6.7: [e28d6b63aeecbda450935fb58db0e682ea8212d3]

CVE-2024-26718: dm-crypt, dm-verity: disable tasklets

Announce: https://lore.kernel.org/linux-cve-announce/2024040344-CVE-2024-26718-7259@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 39d42fa ("dm crypt: add flags to optionally
bypass kcryptd workqueues") in v5.9-rc1.
Introduced by commit 5721d4e ("dm verity: Add optional
"try_verify_in_tasklet" feature") in v6.0-rc1.
These commits are not backported to older stable kernels.
Fixed in v6.8-rc3.

Fixed status
mainline: [0a9bab391e336489169b95cb0d4553d921302189]
stable/6.1: [30884a44e0cedc3dfda8c22432f3ba4078ec2d94]
stable/6.6: [5735a2671ffb70ea29ca83969fe01316ee2ed6fc]
stable/6.7: [0c45a20cbe68bc4d681734f5c03891124a274257]

CVE-2024-26719: nouveau: offload fence uevents work to workqueue

Announce: https://lore.kernel.org/linux-cve-announce/2024040344-CVE-2024-26719-b66e@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc3.

Fixed status
mainline: [39126abc5e20611579602f03b66627d7cd1422f0]
stable/6.6: [cc0037fa592d56e4abb9c7d1c52c4d2dc25cd906]
stable/6.7: [985d053f7633d8b539ab1531738d538efac678a9]

CVE-2024-26720: mm/writeback: fix possible divide-by-zero in
wb_dirty_limits(), again

Announce: https://lore.kernel.org/linux-cve-announce/2024040344-CVE-2024-26720-06fa@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit f678959 ("mm/page-writeback.c: fix divide by zero
in bdi_dirty_limits()") in v3.16.
Fixed in v6.8-rc3.

Fixed status
cip/4.4: [c6db6ae566da0e109616d2517c7047284049d5dc]
cip/4.4-rt: [c6db6ae566da0e109616d2517c7047284049d5dc]
cip/4.4-st: [c6db6ae566da0e109616d2517c7047284049d5dc]
mainline: [9319b647902cbd5cc884ac08a8a6d54ce111fc78]
stable/4.19: [c593d26fb5d577ef31b6e49a31e08ae3ebc1bc1e]
stable/5.10: [81e7d2530d458548b90a5c5e76b77ad5e5d1c0df]
stable/5.15: [5099871b370335809c0fd1abad74d9c7c205d43f]
stable/5.4: [1f12e4b3284d6c863f272eb2de0d4248ed211cf4]
stable/6.1: [16b1025eaa8fc223ab4273ece20d1c3a4211a95d]
stable/6.6: [ec18ec230301583395576915d274b407743d8f6c]
stable/6.7: [65977bed167a92e87085e757fffa5798f7314c9f]

CVE-2024-26721: drm/i915/dsc: Fix the macro that calculates
DSCC_/DSCA_ PPS reg address

Announce: https://lore.kernel.org/linux-cve-announce/2024040345-CVE-2024-26721-3377@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit bd07725 ("drm/i915/vdsc: Add function to read any
PPS register") in v6.7-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc5.

Fixed status
mainline: [962ac2dce56bb3aad1f82a4bbe3ada57a020287c]
stable/6.7: [ff5999fb03f467e1e7159f0ddb199c787f7512b9]

CVE-2024-26722: ASoC: rt5645: Fix deadlock in rt5645_jack_detect_work()

Announce: https://lore.kernel.org/linux-cve-announce/2024040345-CVE-2024-26722-4df2@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit cdba430 ("ASoC: rt5650: add mutex to avoid the
jack detection failure") in v6.7-rc5.
This commit was backported to 4.19, 5.10, 5.15, 5.4, 6.1, and 6.6.
Fixed in v6.8-rc5.

Fixed status
mainline: [6ef5d5b92f7117b324efaac72b3db27ae8bb3082]
stable/4.19: [3dd2d99e2352903d0e0b8769e6c9b8293c7454b2]
stable/5.10: [4a98bc739d0753a5810ce5630943cd7614c7717e]
stable/5.15: [d14b8e2005f36319df9412d42037416d64827f6b]
stable/5.4: [422d5243b9f780abd3d39da2b746e3915677b07d]
stable/6.1: [1f0d7792e9023e8658e901b7b76a555f6aa052ec]
stable/6.6: [050ad2ca0ac169dd9e552075d2c6af1bbb46534c]
stable/6.7: [ed5b8b735369b40d6c1f8ef3e62d369f74b4c491]

CVE-2024-26723: lan966x: Fix crash when adding interface under a lag

Announce: https://lore.kernel.org/linux-cve-announce/2024040345-CVE-2024-26723-49ee@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit cabc9d4 ("net: lan966x: Add lag support for
lan966x") in v6.1-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc5.

Fixed status
mainline: [15faa1f67ab405d47789d4702f587ec7df7ef03e]
stable/6.1: [b9357489c46c7a43999964628db8b47d3a1f8672]
stable/6.6: [48fae67d837488c87379f0c9f27df7391718477c]
stable/6.7: [2a492f01228b7d091dfe38974ef40dccf8f9f2f1]

CVE-2024-26724: net/mlx5: DPLL, Fix possible use after free after
delayed work timer triggers

Announce: https://lore.kernel.org/linux-cve-announce/2024040345-CVE-2024-26724-4e19@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 496fd0a ("mlx5: Implement SyncE support using
DPLL infrastructure") in v6.7-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc5.

Fixed status
mainline: [aa1eec2f546f2afa8c98ec41e5d8ee488165d685]
stable/6.7: [1596126ea50228f0ed96697bae4e9368fda02c56]

CVE-2024-26725: dpll: fix possible deadlock during netlink dump operation

Announce: https://lore.kernel.org/linux-cve-announce/2024040346-CVE-2024-26725-d16b@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 9d71b54 ("dpll: netlink: Add DPLL framework base
functions") in v6.7-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc5.

Fixed status
mainline: [53c0441dd2c44ee93fddb5473885fd41e4bc2361]
stable/6.7: [087739cbd0d0b87b6cec2c0799436ac66e24acc8]

CVE-2024-26726: btrfs: don't drop extent_map for free space inode on write error

Announce: https://lore.kernel.org/linux-cve-announce/2024040346-CVE-2024-26726-fed0@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc5.
Backporting the fix to 4.19
(https://lore.kernel.org/stable/2024021802-crunchy-presoak-d1f4@gregkh/),
5.4 (https://lore.kernel.org/stable/2024021800-willed-chug-3616@gregkh/),
5.10 (https://lore.kernel.org/stable/2024021858-sharpie-diffusive-52e1@gregkh/),
and
5.15 (https://lore.kernel.org/stable/2024021856-vigorous-supper-1ca1@gregkh/)
were failed.

Fixed status
mainline: [5571e41ec6e56e35f34ae9f5b3a335ef510e0ade]
stable/6.1: [02f2b95b00bf57d20320ee168b30fb7f3db8e555]
stable/6.6: [7bddf18f474f166c19f91b2baf67bf7c5eda03f7]
stable/6.7: [a4b7741c8302e28073bfc6dd1c2e73598e5e535e]

CVE-2024-26727: btrfs: do not ASSERT() if the newly created subvolume
already got read

Announce: https://lore.kernel.org/linux-cve-announce/2024040346-CVE-2024-26727-3ec3@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 2dfb1e4 ("btrfs: preallocate anon block device at
first phase of snapshot creation") in v5.9-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc4.

Fixed status
mainline: [e03ee2fe873eb68c1f9ba5112fee70303ebf9dfb]
stable/5.10: [3f5d47eb163bceb1b9e613c9003bae5fefc0046f]
stable/5.15: [e31546b0f34af21738c4ceac47d662c00ee6382f]
stable/6.1: [66b317a2fc45b2ef66527ee3f8fa08fb5beab88d]
stable/6.6: [833775656d447c545133a744a0ed1e189ce61430]
stable/6.7: [5a172344bfdabb46458e03708735d7b1a918c468]

CVE-2024-26728: drm/amd/display: fix null-pointer dereference on edid reading

Announce: https://lore.kernel.org/linux-cve-announce/2024040357-CVE-2024-26728-316a@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 0e859fa ("drm/amd/display: Remove unwanted drm
edid references") in v6.7-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc6.

Fixed status
mainline: [9671761792156f2339627918bafcd713a8a6f777]
stable/6.7: [2d392f7268a1a9bfbd98c831f0f4c964e59aa145]

CVE-2024-26729: drm/amd/display: Fix potential null pointer
dereference in dc_dmub_srv

Announce: https://lore.kernel.org/linux-cve-announce/2024040357-CVE-2024-26729-2f3e@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 028bac5 ("drm/amd/display: decouple dmcub
execution to reduce lock granularity") in v6.7-rc1.
Introduced by commit 65138eb ("drm/amd/display: Add DCN35 DMUB") in v6.7-rc1.
These commits are not backported to older stable kernels.
Fixed in v6.8-rc6.

Fixed status
mainline: [d2b48f340d9e4a8fbeb1cdc84cd8da6ad143a907]
stable/6.7: [351080ba3414c96afff0f1338b4aeb2983195b80]

CVE-2024-26730: hwmon: (nct6775) Fix access to temperature
configuration registers

Announce: https://lore.kernel.org/linux-cve-announce/2024040358-CVE-2024-26730-4c35@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit b7f1f7b ("hwmon: (nct6775) Additional TEMP
registers for nct6799") in v6.6-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc6.

Fixed status
mainline: [d56e460e19ea8382f813eb489730248ec8d7eb73]
stable/6.6: [f006c45a3ea424f8f6c8e4b9283bc245ce2a4d0f]
stable/6.7: [c196387820c9214c5ceaff56d77303c82514b8b1]

CVE-2024-26731: bpf, sockmap: Fix NULL pointer dereference in
sk_psock_verdict_data_ready()

Announce: https://lore.kernel.org/linux-cve-announce/2024040358-CVE-2024-26731-e084@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 6df7f76 ("bpf, sockmap: Wake up polling after
data copy") in v6.4-rc4.
This commit was backported to 6.1.
Fixed in v6.8-rc6.

Fixed status
mainline: [4cd12c6065dfcdeba10f49949bffcf383b3952d8]
stable/6.1: [4588b13abcbd561ec67f5b3c1cb2eff690990a54]
stable/6.6: [9b099ed46dcaf1403c531ff02c3d7400fa37fa26]
stable/6.7: [d61608a4e394f23e0dca099df9eb8e555453d949]

CVE-2024-26732: net: implement lockless setsockopt(SO_PEEK_OFF)

Announce: https://lore.kernel.org/linux-cve-announce/2024040358-CVE-2024-26732-8cda@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 859051d ("bpf: Implement cgroup sockaddr hooks
for unix sockets") in v6.7-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc6.

Fixed status
mainline: [56667da7399eb19af857e30f41bea89aa6fa812c]
stable/6.7: [897f75e2cde8a5f9f7529b55249af1fa4248c83b]

CVE-2024-26733: arp: Prevent overflow in arp_req_get().

Announce: https://lore.kernel.org/linux-cve-announce/2024040358-CVE-2024-26733-617f@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 1da177e ("Linux-2.6.12-rc2") in v2.6.12.
Fixed in v6.8-rc6.

Fixed status
mainline: [a7d6027790acea24446ddd6632d394096c0f4667]
stable/5.10: [dbc9b22d0ed319b4e29034ce0a3fe32a3ee2c587]
stable/5.15: [97eaa2955db4120ce6ec2ef123e860bc32232c50]
stable/6.1: [f119f2325ba70cbfdec701000dcad4d88805d5b0]
stable/6.6: [a3f2c083cb575d80a7627baf3339e78fedccbb91]
stable/6.7: [3ab0d6f8289ba8402ca95a9fc61a34909d5e1f3a]

CVE-2024-26734: devlink: fix possible use-after-free and memory leaks
in devlink_init()

Announce: https://lore.kernel.org/linux-cve-announce/2024040359-CVE-2024-26734-277b@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 687125b ("devlink: split out core code") in v6.3-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc6.

Fixed status
mainline: [def689fc26b9a9622d2e2cb0c4933dd3b1c8071c]
stable/6.6: [919092bd5482b7070ae66d1daef73b600738f3a2]
stable/6.7: [e91d3561e28d7665f4f837880501dc8755f635a9]

CVE-2024-26735: ipv6: sr: fix possible use-after-free and null-ptr-deref

Announce: https://lore.kernel.org/linux-cve-announce/2024040359-CVE-2024-26735-462f@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 915d7e5 ("ipv6: sr: add code base for control
plane support of SR-IPv6") in v4.10-rc1.
This commit is not backported to 4.4.
Fixed in v6.8-rc6.

Fixed status
mainline: [5559cea2d5aa3018a5f00dd2aca3427ba09b386b]
stable/4.19: [953f42934533c151f440cd32390044d2396b87aa]
stable/5.10: [65c38f23d10ff79feea1e5d50b76dc7af383c1e6]
stable/5.15: [91b020aaa1e59bfb669d34c968e3db3d5416bcee]
stable/5.4: [82831e3ff76ef09fb184eb93b79a3eb3fb284f1d]
stable/6.1: [8391b9b651cfdf80ab0f1dc4a489f9d67386e197]
stable/6.6: [9e02973dbc6a91e40aa4f5d87b8c47446fbfce44]
stable/6.7: [02b08db594e8218cfbc0e4680d4331b457968a9b]

CVE-2024-26736: afs: Increase buffer size in afs_update_volume_status()

Announce: https://lore.kernel.org/linux-cve-announce/2024040359-CVE-2024-26736-284d@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit d2ddc77 ("afs: Overhaul volume and server record
caching and fileserver rotation") in v4.15-rc1.
This commit is not backported to 4.4.
Fixed in v6.8-rc6.

Fixed status
mainline: [6ea38e2aeb72349cad50e38899b0ba6fbcb2af3d]
stable/5.10: [d9b5e2b7a8196850383c70d099bfd39e81ab6637]
stable/5.15: [e56662160fc24d28cb75ac095cc6415ae1bda43e]
stable/5.4: [5c27d85a69fa16a08813ba37ddfb4bbc9a1ed6b5]
stable/6.1: [e8530b170e464017203e3b8c6c49af6e916aece1]
stable/6.6: [6e6065dd25b661420fac19c34282b6c626fcd35e]
stable/6.7: [d34a5e57632bb5ff825196ddd9a48ca403626dfa]

CVE-2024-26737: bpf: Fix racing between bpf_timer_cancel_and_free and
bpf_timer_cancel

Announce: https://lore.kernel.org/linux-cve-announce/2024040359-CVE-2024-26737-a9c3@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit b00628b ("bpf: Introduce bpf timers.") in v5.15-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc6.

Fixed status
mainline: [0281b919e175bb9c3128bd3872ac2903e9436e3f]
stable/5.15: [5268bb02107b9eedfdcd51db75b407d10043368c]
stable/6.1: [addf5e297e6cbf5341f9c07720693ca9ba0057b5]
stable/6.6: [8327ed12e8ebc5436bfaa1786c49988894f9c8a6]
stable/6.7: [7d80a9e745fa5b47da3bca001f186c02485c7c33]

CVE-2024-26738: powerpc/pseries/iommu: DLPAR add doesn't completely
initialize pci_controller

Announce: https://lore.kernel.org/linux-cve-announce/2024040300-CVE-2024-26738-844b@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit a940904 ("powerpc/iommu: Add iommu_ops to report
capabilities and allow blocking domains") in v6.4-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc6.

Fixed status
mainline: [a5c57fd2e9bd1c8ea8613a8f94fd0be5eccbf321]
stable/6.6: [b8315b2e25b4e68e42fcb74630f824b9a5067765]
stable/6.7: [46e36ebd5e00a148b67ed77c1d31675996f77c25]

CVE-2024-26739: net/sched: act_mirred: don't override retval if we
already lost the skb

Announce: https://lore.kernel.org/linux-cve-announce/2024040300-CVE-2024-26739-170e@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit e5cf1ba ("act_mirred: use TC_ACT_REINSERT when
possible") in v4.19-rc1.
This commit is not backported to 4.4.
Fixed in v6.8-rc6.

Fixed status
mainline: [166c2c8a6a4dc2e4ceba9e10cfe81c3e469e3210]
stable/6.6: [28cdbbd38a4413b8eff53399b3f872fd4e80db9d]
stable/6.7: [f4e294bbdca8ac8757db436fc82214f3882fc7e7]

CVE-2024-26740: net/sched: act_mirred: use the backlog for mirred ingress

Announce: https://lore.kernel.org/linux-cve-announce/2024040300-CVE-2024-26740-4d6f@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 53592b3 ("net/sched: act_mirred: Implement
ingress actions") in v4.10-rc1.
This commit is backported to 4.4.
Fixed in v6.8-rc6.

Fixed status
mainline: [52f671db18823089a02f07efc04efdb2272ddc17]
stable/6.6: [7c787888d164689da8b1b115f3ef562c1e843af4]
stable/6.7: [60ddea1600bc476e0f5e02bce0e29a460ccbf0be]

CVE-2024-26741: dccp/tcp: Unhash sk from ehash for tb2 alloc failure
after check_estalblished().

Announce: https://lore.kernel.org/linux-cve-announce/2024040300-CVE-2024-26741-961e@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 28044fc ("net: Add a bhash2 table hashed by port
and address") in v6.1-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc6.

Fixed status
mainline: [66b60b0c8c4a163b022a9f0ad6769b0fd3dc662f]
stable/6.1: [729bc77af438a6e67914c97f6f3d3af8f72c0131]
stable/6.6: [334a8348b2df26526f3298848ad6864285592caf]
stable/6.7: [f8c4a6b850882bc47aaa864b720c7a2ee3102f39]

CVE-2024-26742: scsi: smartpqi: Fix disable_managed_interrupts

Announce: https://lore.kernel.org/linux-cve-announce/2024040301-CVE-2024-26742-1b19@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit cf15c3e ("scsi: smartpqi: Add module param to
disable managed ints") in v6.0-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc6.

Fixed status
mainline: [5761eb9761d2d5fe8248a9b719efc4d8baf1f24a]
stable/6.1: [3c31b18a8dd8b7bf36af1cd723d455853b8f94fe]
stable/6.6: [4f5b15c15e6016efb3e14582d02cc4ddf57227df]
stable/6.7: [b9433b25cb06c415c9cb24782599649a406c8d6d]

CVE-2024-26743: RDMA/qedr: Fix qedr_create_user_qp error flow

Announce: https://lore.kernel.org/linux-cve-announce/2024040301-CVE-2024-26743-6034@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit df15856 ("RDMA/qedr: restructure functions that
create/destroy QPs") in v4.11-rc1.
This commit is not backported to 4.4.
Fixed in v6.8-rc6.

Fixed status
mainline: [5ba4e6d5863c53e937f49932dee0ecb004c65928]
stable/5.10: [5639414a52a29336ffa1ede80a67c6d927acbc5a]
stable/5.15: [135e5465fefa463c5ec93c4eede48b9fedac894a]
stable/6.1: [7f31a244c753aacf40b71d01f03ca6742f81bbbc]
stable/6.6: [95175dda017cd4982cd47960536fa1de003d3298]
stable/6.7: [bab8875c06ebda5e01c5c4cab30022aed85c14e6]

CVE-2024-26744: RDMA/srpt: Support specifying the srpt_service_guid parameter

Announce: https://lore.kernel.org/linux-cve-announce/2024040301-CVE-2024-26744-d344@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit a42d985 ("ib_srpt: Initial SRP Target merge for
v3.3-rc1") in v3.3-rc1.
Fixed in v6.8-rc6.

Fixed status
mainline: [fdfa083549de5d50ebf7f6811f33757781e838c0]
stable/4.19: [84f1dac960cfa210a3b7a7522e6c2320ae91932b]
stable/5.10: [5a5c039dac1b1b7ba3e91c791f4421052bf79b82]
stable/5.15: [989af2f29342a9a7c7515523d879b698ac8465f4]
stable/6.1: [aee4dcfe17219fe60f2821923adea98549060af8]
stable/6.6: [fe2a73d57319feab4b3b175945671ce43492172f]
stable/6.7: [c99a827d3cff9f84e1cb997b7cc6386d107aa74d]

CVE-2024-26747: usb: roles: fix NULL pointer issue when put module's reference

Announce: https://lore.kernel.org/linux-cve-announce/2024040301-CVE-2024-26747-50b0@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 5c54fca ("usb: roles: Take care of driver module
reference counting") in v4.19-rc6.
This commit is not backported to 4.4.
Fixed in v6.8-rc6.

Fixed status
mainline: [1c9be13846c0b2abc2480602f8ef421360e1ad9e]
stable/5.10: [e279bf8e51893e1fe160b3d8126ef2dd00f661e1]
stable/5.15: [ef982fc41055fcebb361a92288d3225783d12913]
stable/6.1: [0158216805ca7e498d07de38840d2732166ae5fa]
stable/6.6: [4b45829440b1b208948b39cc71f77a37a2536734]
stable/6.7: [01f82de440f2ab07c259b7573371e1c42e5565db]

CVE-2024-26748: usb: cdns3: fix memory double free when handle zero packet

Announce: https://lore.kernel.org/linux-cve-announce/2024040302-CVE-2024-26748-f000@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 7733f6c ("usb: cdns3: Add Cadence USB3 DRD
Driver") in v5.4-rc1.
This commit is not backported to 4.x.
Fixed in v6.8-rc6.

Fixed status
mainline: [5fd9e45f1ebcd57181358af28506e8a661a260b3]
stable/5.10: [1e204a8e9eb514e22a6567fb340ebb47df3f3a48]
stable/5.15: [3a2a909942b5335b7ea66366d84261b3ed5f89c8]
stable/5.4: [aad6132ae6e4809e375431f8defd1521985e44e7]
stable/6.1: [9a52b694b066f299d8b9800854a8503457a8b64c]
stable/6.6: [70e8038813f9d3e72df966748ebbc40efe466019]
stable/6.7: [92d20406a3d4ff3e8be667c79209dc9ed31df5b3]

CVE-2024-26749: usb: cdns3: fixed memory use after free at
cdns3_gadget_ep_disable()

Announce: https://lore.kernel.org/linux-cve-announce/2024040302-CVE-2024-26749-eac4@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 7733f6c ("usb: cdns3: Add Cadence USB3 DRD
Driver") in v5.4-rc1.
This commit is not backported to 4.x.
Fixed in v6.8-rc6.

Fixed status
mainline: [cd45f99034b0c8c9cb346dd0d6407a95ca3d36f6]
stable/5.10: [b40328eea93c75a5645891408010141a0159f643]
stable/5.15: [4e5c73b15d95452c1ba9c771dd013a3fbe052ff3]
stable/5.4: [cfa9abb5570c489dabf6f7fb3a066cc576fc8824]
stable/6.1: [2134e9906e17b1e5284300fab547869ebacfd7d9]
stable/6.6: [29e42e1578a10c611b3f1a38f3229b2d664b5d16]
stable/6.7: [9a07244f614bc417de527b799da779dcae780b5d]

CVE-2024-26751: ARM: ep93xx: Add terminator to gpiod_lookup_table

Announce: https://lore.kernel.org/linux-cve-announce/2024040302-CVE-2024-26751-fd31@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit b2e6355 ("i2c: gpio: Convert to use descriptors")
in v4.15-rc1.
This commit is not backported to 4.4.
Fixed in v6.8-rc6.

Fixed status
mainline: [fdf87a0dc26d0550c60edc911cda42f9afec3557]
stable/4.19: [9e200a06ae2abb321939693008290af32b33dd6e]
stable/5.10: [70d92abbe29692a3de8697ae082c60f2d21ab482]
stable/5.15: [eec6cbbfa1e8d685cc245cfd5626d0715a127a48]
stable/5.4: [999a8bb70da2946336327b4480824d1691cae1fa]
stable/6.1: [786f089086b505372fb3f4f008d57e7845fff0d8]
stable/6.6: [97ba7c1f9c0a2401e644760d857b2386aa895997]
stable/6.7: [6abe0895b63c20de06685c8544b908c7e413efa8]

CVE-2024-26752: l2tp: pass correct message length to ip6_append_data

Announce: https://lore.kernel.org/linux-cve-announce/2024040302-CVE-2024-26752-cb0a@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 9d4c758 ("ipv4, ipv6: Fix handling of transhdrlen
in __ip{,6}_append_data()") in v6.6-rc5.
Fixed in v6.8-rc6.

Fixed status
cip/4.4: [e4d9ba7b6e13a2d6611a039d01f1f6b7313667db]
cip/4.4-rt: [e4d9ba7b6e13a2d6611a039d01f1f6b7313667db]
cip/4.4-st: [e4d9ba7b6e13a2d6611a039d01f1f6b7313667db]
mainline: [359e54a93ab43d32ee1bff3c2f9f10cb9f6b6e79]
stable/4.19: [4c3ce64bc9d36ca9164dd6c77ff144c121011aae]
stable/5.10: [dcb4d14268595065c85dc5528056713928e17243]
stable/5.15: [0da15a70395182ee8cb75716baf00dddc0bea38d]
stable/5.4: [c1d3a84a67db910ce28a871273c992c3d7f9efb5]
stable/6.1: [13cd1daeea848614e585b2c6ecc11ca9c8ab2500]
stable/6.6: [804bd8650a3a2bf3432375f8c97d5049d845ce56]
stable/6.7: [83340c66b498e49353530e41542500fc8a4782d6]

CVE-2024-26753: crypto: virtio/akcipher - Fix stack overflow on memcpy

Announce: https://lore.kernel.org/linux-cve-announce/2024040303-CVE-2024-26753-b93a@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 59ca6c9 ("virtio-crypto: implement RSA
algorithm") in v5.18-rc1.
This commit is backported to 5.10.
Fixed in v6.8-rc6.

Fixed status
mainline: [c0ec2a712daf133d9996a8a1b7ee2d4996080363]
stable/5.10: [37077ed16c7793e21b005979d33f8a61565b7e86]
stable/6.1: [62f361bfea60c6afc3df09c1ad4152e6507f6f47]
stable/6.6: [b0365460e945e1117b47cf7329d86de752daff63]
stable/6.7: [ef1e47d50324e232d2da484fe55a54274eeb9bc1]

CVE-2024-26754: gtp: fix use-after-free and null-ptr-deref in
gtp_genl_dump_pdp()

Announce: https://lore.kernel.org/linux-cve-announce/2024040303-CVE-2024-26754-b34f@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 459aa66 ("gtp: add initial driver for datapath of
GPRS Tunneling Protocol (GTP-U)") in v4.7-rc1.
This commit is not backported to 4.4.
Fixed in v6.8-rc6.

Fixed status
mainline: [136cfaca22567a03bbb3bf53a43d8cb5748b80ec]
stable/4.19: [f0ecdfa679189d26aedfe24212d4e69e42c2c861]
stable/5.10: [2e534fd15e5c2ca15821c897352cf0e8a3e30dca]
stable/5.15: [a576308800be28f2eaa099e7caad093b97d66e77]
stable/5.4: [f8cbd1791900b5d96466eede8e9439a5b9ca4de7]
stable/6.1: [3963f16cc7643b461271989b712329520374ad2a]
stable/6.6: [ba6b8b02a3314e62571a540efa96560888c5f03e]
stable/6.7: [5013bd54d283eda5262c9ae3bcc966d01daf8576]

CVE-2024-26755: md: Don't suspend the array for interrupted reshape

Announce: https://lore.kernel.org/linux-cve-announce/2024040303-CVE-2024-26755-947e@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit bc08041 ("md: suspend array in md_start_sync() if
array need reconfiguration") in v6.7-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc6.

Fixed status
mainline: [9e46c70e829bddc24e04f963471e9983a11598b7]
stable/6.7: [60d6130d0ac1d883ed93c2a1e10aadb60967fd48]

CVE-2024-26756: md: Don't register sync_thread for reshape directly

Announce: https://lore.kernel.org/linux-cve-announce/2024040303-CVE-2024-26756-135f@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit f670557 ("[PATCH] md: Checkpoint and allow
restart of raid5 reshape") in v2.6.20.16.
Introduced by commit f52f5c7 ("md: fix stopping sync thread") in v6.7-rc5.
Fixed in v6.8-rc6.

Fixed status
mainline: [ad39c08186f8a0f221337985036ba86731d6aafe]
stable/6.7: [13b520fb62b772e408f9b79c5fe18ad414e90417]

CVE-2024-26757: md: Don't ignore read-only array in md_check_recovery()

Announce: https://lore.kernel.org/linux-cve-announce/2024040304-CVE-2024-26757-7f96@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit ecbfb9f ("dm raid: add raid level takeover
support") in v4.8-rc1.
Introduced by commit f52f5c7 ("md: fix stopping sync thread") in v6.7-rc5.
Fixed in v6.8-rc6.

Fixed status
mainline: [55a48ad2db64737f7ffc0407634218cc6e4c513b]
stable/6.7: [2ea169c5a0b1134d573d07fc27a16f327ad0e7d3]

CVE-2024-26758: md: Don't ignore suspended array in md_check_recovery()

Announce: https://lore.kernel.org/linux-cve-announce/2024040304-CVE-2024-26758-dcc3@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 68866e4 ("MD: no sync IO while suspended") in v3.0-rc4.
Introduced by commit f52f5c7 ("md: fix stopping sync thread") in v6.7-rc5.
Fixed in v6.8-rc6.

Fixed status
mainline: [1baae052cccd08daf9a9d64c3f959d8cdb689757]
stable/6.7: [a55f0d6179a19c6b982e2dc344d58c98647a3be0]

CVE-2024-26759: mm/swap: fix race when skipping swapcache

Announce: https://lore.kernel.org/linux-cve-announce/2024040304-CVE-2024-26759-45f1@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 0bcac06 ("mm, swap: skip swapcache for swapin of
synchronous device") in v4.15-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc6.

Fixed status
mainline: [13ddaf26be324a7f951891ecd9ccd04466d27458]
stable/6.1: [2dedda77d4493f3e92e414b272bfa60f1f51ed95]
stable/6.6: [305152314df82b22cf9b181f3dc5fc411002079a]
stable/6.7: [d183a4631acfc7af955c02a02e739cec15f5234d]

CVE-2024-26760: scsi: target: pscsi: Fix bio_put() for error case

Announce: https://lore.kernel.org/linux-cve-announce/2024040305-CVE-2024-26760-560a@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 066ff57 ("block: turn bio_kmalloc into a simple
kmalloc wrapper") in v5.19-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc6.

Fixed status
mainline: [de959094eb2197636f7c803af0943cb9d3b35804]
stable/6.1: [f49b20fd0134da84a6bd8108f9e73c077b7d6231]
stable/6.6: [4ebc079f0c7dcda1270843ab0f38ab4edb8f7921]
stable/6.7: [1cfe9489fb563e9a0c9cdc5ca68257a44428c2ec]

CVE-2024-26761: cxl/pci: Fix disabling memory if DVSEC CXL Range does
not match a CFMWS window

Announce: https://lore.kernel.org/linux-cve-announce/2024040305-CVE-2024-26761-0646@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 34e37b4 ("cxl/port: Enable HDM Capability after
validating DVSEC Ranges") in v5.19-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc6.

Fixed status
mainline: [0cab687205986491302cd2e440ef1d253031c221]
stable/6.1: [031217128990d7f0ab8c46db1afb3cf1e075fd29]
stable/6.6: [2cc1a530ab31c65b52daf3cb5d0883c8b614ea69]
stable/6.7: [3a3181a71935774bda2398451256d7441426420b]

CVE-2024-26762: cxl/pci: Skip to handle RAS errors if CXL.mem device is detached

Announce: https://lore.kernel.org/linux-cve-announce/2024040305-CVE-2024-26762-b719@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 6ac0788 ("cxl/pci: Add RCH downstream port error
logging") in v6.7-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc6.

Fixed status
mainline: [eef5c7b28dbecd6b141987a96db6c54e49828102]
stable/6.7: [21e5e84f3f63fdf44e49642a6e45cd895e921a84]

CVE-2024-26763: dm-crypt: don't modify the data when using
authenticated encryption

Announce: https://lore.kernel.org/linux-cve-announce/2024040305-CVE-2024-26763-4627@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc6.
This fix mab be applied to Linux 4.4.

Fixed status
mainline: [50c70240097ce41fe6bce6478b80478281e4d0f7]
stable/4.19: [43a202bd552976497474ae144942e32cc5f34d7e]
stable/5.10: [3c652f6fa1e1f9f02c3fbf359d260ad153ec5f90]
stable/5.15: [1a4371db68a31076afbe56ecce34fbbe6c80c529]
stable/5.4: [0dccbb93538fe89a86c6de31d4b1c8c560848eaa]
stable/6.1: [e08c2a8d27e989f0f5b0888792643027d7e691e6]
stable/6.6: [64ba01a365980755732972523600a961c4266b75]
stable/6.7: [d9e3763a505e50ba3bd22846f2a8db99429fb857]

CVE-2024-26764: fs/aio: Restrict kiocb_set_cancel_fn() to I/O
submitted via libaio

Announce: https://lore.kernel.org/linux-cve-announce/2024040306-CVE-2024-26764-c1e7@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc6.
The aio_complete_rw() was introduced by commit 54843f ("aio: refactor
read/write iocb setup") in 4.18-rc1.

Fixed status
mainline: [b820de741ae48ccf50dd95e297889c286ff4f760]
stable/4.19: [337b543e274fe7a8f47df3c8293cc6686ffa620f]
stable/5.10: [ea1cd64d59f22d6d13f367d62ec6e27b9344695f]
stable/5.15: [d7b6fa97ec894edd02f64b83e5e72e1aa352f353]
stable/5.4: [b4eea7a05ee0ab5ab0514421e6ba8c5d249cf942]
stable/6.1: [18f614369def2a11a52f569fe0f910b199d13487]
stable/6.6: [e7e23fc5d5fe422827c9a43ecb579448f73876c7]
stable/6.7: [1dc7d74fe456944a9b1c57bd776280249f441ac6]

CVE-2024-26765: LoongArch: Disable IRQ before init_fn() for nonboot CPUs

Announce: https://lore.kernel.org/linux-cve-announce/2024040306-CVE-2024-26765-157f@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc6.
LoongArch was introduced in 5.19. So 4.x, 5.4, 5.10, and 5.15 are not affected.

Fixed status
mainline: [1001db6c42e4012b55e5ee19405490f23e033b5a]
stable/6.1: [a262b78dd085dbe9b3c75dc1d9c4cd102b110b53]
stable/6.6: [dffdf7c783ef291eef38a5a0037584fd1a7fa464]
stable/6.7: [8bf2ca8c60712af288b88ba80f8e4df4573d923f]

CVE-2024-26766: IB/hfi1: Fix sdma.h tx->num_descs off-by-one error

Announce: https://lore.kernel.org/linux-cve-announce/2024040306-CVE-2024-26766-6b6a@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit fd8958e ("IB/hfi1: Fix sdma.h tx->num_descs
off-by-one errors") in v6.3-rc1.
This commit was backported to 4.19, 5.10, 5.15, 5.4, adn 6.1."
Fixed in v6.8-rc6.

Fixed status
mainline: [e6f57c6881916df39db7d95981a8ad2b9c3458d6]
stable/4.19: [115b7f3bc1dce590a6851a2dcf23dc1100c49790]
stable/5.10: [3f38d22e645e2e994979426ea5a35186102ff3c2]
stable/5.15: [47ae64df23ed1318e27bd9844e135a5e1c0e6e39]
stable/5.4: [5833024a9856f454a964a198c63a57e59e07baf5]
stable/6.1: [52dc9a7a573dbf778625a0efca0fca55489f084b]
stable/6.6: [a2fef1d81becf4ff60e1a249477464eae3c3bc2a]
stable/6.7: [9034a1bec35e9f725315a3bb6002ef39666114d9]

CVE-2024-26767: drm/amd/display: fixed integer types and null check locations

Announce: https://lore.kernel.org/linux-cve-announce/2024040306-CVE-2024-26767-bdac@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc5.
Backporting the fix to 4.19
(https://lore.kernel.org/stable/20240327122712.2841726-1-sashal@kernel.org/),
5.4 (https://lore.kernel.org/stable/20240327122323.2838480-1-sashal@kernel.org/),
5.10 (https://lore.kernel.org/stable/20240327121940.2835388-1-sashal@kernel.org/),
5.15 (https://lore.kernel.org/stable/20240327121618.2832619-1-sashal@kernel.org/),
and
6.1 (https://lore.kernel.org/stable/20240327121305.2830053-1-sashal@kernel.org/)
were failed.

The link_validation.c was introduced by commit 5461888
("drm/amd/display: break down dc_link.c") in 6.3-rc1.
The bios_parser2.c was introduced by commit ae79c310
("drm/amd/display: Add DCE12 bios parser support") in 4.15-rc1.
So, Linux 4.4 may not be affected.

Fixed status
mainline: [0484e05d048b66d01d1f3c1d2306010bb57d8738]
stable/6.6: [71783d1ff65204d69207fd156d4b2eb1d3882375]
stable/6.7: [beea9ab9080cd2ef46296070bb327af066ee09d7]

CVE-2024-26768: LoongArch: Change acpi_core_pic[NR_CPUS] to
acpi_core_pic[MAX_CORE_PIC]

Announce: https://lore.kernel.org/linux-cve-announce/2024040307-CVE-2024-26768-efa4@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc4.
LoongArch was introduced in 5.19. So 4.x, 5.4, 5.10, and 5.15 are not affected.

Fixed status
mainline: [4551b30525cf3d2f026b92401ffe241eb04dfebe]
stable/6.6: [88e189bd16e5889e44a41b3309558ebab78b9280]
stable/6.7: [0f6810e39898af2d2cabd9313e4dbc945fb5dfdd]

CVE-2024-26769: nvmet-fc: avoid deadlock on delete association path

Announce: https://lore.kernel.org/linux-cve-announce/2024040307-CVE-2024-26769-e9cc@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc3.
Affected file fc.c was introduced by commit c5343203 ("nvme-fabrics:
Add target support for FC transport") in 4.10-rc1.

Fixed status
mainline: [710c69dbaccdac312e32931abcb8499c1525d397]
stable/5.15: [5e0bc09a52b6169ce90f7ac6e195791adb16cec4]
stable/6.1: [9e6987f8937a7bd7516aa52f25cb7e12c0c92ee8]
stable/6.6: [eaf0971fdabf2a93c1429dc6bedf3bbe85dffa30]
stable/6.7: [1d86f79287206deec36d63b89c741cf542b6cadd]

CVE-2024-26770: HID: nvidia-shield: Add missing null pointer checks to
LED initialization

Announce: https://lore.kernel.org/linux-cve-announce/2024040307-CVE-2024-26770-1c08@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc3.
Calling devm_kasprintf() was added by commit 3ab196f ("HID:
nvidia-shield: Add battery support for Thunderstrike") in 6.6-rc1 and
7fe1fed4 ("HID: nvidia-shield: Update Thunderstrike LED instance name
to use id") in 6.6-rc1.
These commits are not backported to older stable kernels.

Fixed status
mainline: [b6eda11c44dc89a681e1c105f0f4660e69b1e183]
stable/6.6: [83527a13740f57b45f162e3af4c7db4b88521100]
stable/6.7: [e71cc4a1e584293deafff1a7dea614b0210d0443]

CVE-2024-26771: dmaengine: ti: edma: Add some null pointer checks to
the edma_probe

Announce: https://lore.kernel.org/linux-cve-announce/2024040307-CVE-2024-26771-b6de@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc3.
Calling devm_kasprintf() was added by 2b6b3b7 ("ARM/dmaengine: edma:
Merge the two drivers under drivers/dma/") in 4.4-rc1.
The drivers/dma/ti/edma.c is drivers/dma/edma.c in Linux 4.4.

Fixed status
mainline: [6e2276203ac9ff10fc76917ec9813c660f627369]
stable/5.10: [c432094aa7c9970f2fa10d2305d550d3810657ce]
stable/5.15: [4fe4e5adc7d29d214c59b59f61db73dec505ca3d]
stable/6.1: [9d508c897153ae8dd79303f7f035f078139f6b49]
stable/6.6: [7b24760f3a3c7ae1a176d343136b6c25174b7b27]
stable/6.7: [f2a5e30d1e9a629de6179fa23923a318d5feb29e]

CVE-2024-26772: ext4: avoid allocating blocks from corrupted group in
ext4_mb_find_by_goal()

Announce: https://lore.kernel.org/linux-cve-announce/2024040308-CVE-2024-26772-5168@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc3.

Fixed status
cip/4.4: [d545ccbb16d47682e28a877a561e69aed6918d27]
cip/4.4-rt: [d545ccbb16d47682e28a877a561e69aed6918d27]
cip/4.4-st: [d545ccbb16d47682e28a877a561e69aed6918d27]
mainline: [832698373a25950942c04a512daa652c18a9b513]
stable/4.19: [5a6dcc4ad0f7f7fa8e8d127b5526e7c5f2d38a43]
stable/5.10: [ffeb72a80a82aba59a6774b0611f792e0ed3b0b7]
stable/5.15: [8de8305a25bfda607fc13475ebe84b978c96d7ff]
stable/5.4: [6b92b1bc16d691c95b152c6dbf027ad64315668d]
stable/6.1: [d639102f4cbd4cb65d1225dba3b9265596aab586]
stable/6.6: [d3bbe77a76bc52e9d4d0a120f1509be36e25c916]
stable/6.7: [21dbe20589c7f48e9c5d336ce6402bcebfa6d76a]

CVE-2024-26773: ext4: avoid allocating blocks from corrupted group in
ext4_mb_try_best_found()

Announce: https://lore.kernel.org/linux-cve-announce/2024040308-CVE-2024-26773-a314@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc3.

Fixed status
cip/4.4: [24f29b76aab92974ff562960a3bc720aa36dd80c]
cip/4.4-rt: [24f29b76aab92974ff562960a3bc720aa36dd80c]
cip/4.4-st: [24f29b76aab92974ff562960a3bc720aa36dd80c]
mainline: [4530b3660d396a646aad91a787b6ab37cf604b53]
stable/4.19: [21f8cfe79f776287459343e9cfa6055af61328ea]
stable/5.10: [927794a02169778c9c2e7b25c768ab3ea8c1dc03]
stable/5.15: [4c21fa60a6f4606f6214a38f50612b17b2f738f5]
stable/5.4: [260fc96283c0f594de18a1b045faf6d8fb42874d]
stable/6.1: [f97e75fa4e12b0aa0224e83fcbda8853ac2adf36]
stable/6.6: [0184747b552d6b5a14db3b7fcc3b792ce64dedd1]
stable/6.7: [a2576ae9a35c078e488f2c573e9e6821d651fbbe]

CVE-2024-26774: ext4: avoid dividing by 0 in
mb_update_avg_fragment_size() when block bitmap corrupt

Announce: https://lore.kernel.org/linux-cve-announce/2024040308-CVE-2024-26774-52d9@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc3.
The mb_update_avg_fragment_size() was introduced by commit 196e402
("ext4: improve cr 0 / cr 1 group scanning") in 5.13-rc1.

Fixed status
mainline: [993bf0f4c393b3667830918f9247438a8f6fdb5b]
stable/5.15: [687061cfaa2ac3095170e136dd9c29a4974f41d4]
stable/6.1: [8b40eb2e716b503f7a4e1090815a17b1341b2150]
stable/6.6: [f32d2a745b02123258026e105a008f474f896d6a]
stable/6.7: [8cf9cc602cfb40085967c0d140e32691c8b71cf3]

CVE-2024-26775: aoe: avoid potential deadlock at set_capacity

Announce: https://lore.kernel.org/linux-cve-announce/2024040309-CVE-2024-26775-8dc1@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc2.
It seems as if 4.x and 5.x kernels are affected.

Fixed status
mainline: [e169bd4fb2b36c4b2bee63c35c740c85daeb2e86]
stable/6.1: [2d623c94fbba3554f4446ba6f3c764994e8b0d26]
stable/6.6: [673629018ba04906899dcb631beec34d871f709c]
stable/6.7: [19a77b27163820f793b4d022979ffdca8f659b77]

CVE-2024-26776: spi: hisi-sfc-v3xx: Return IRQ_NONE if no interrupts
were detected

Announce: https://lore.kernel.org/linux-cve-announce/2024040309-CVE-2024-26776-8119@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc2.
The hisi_sfc_v3xx_isr() was introduced by commit b1dd56512 ("spi:
hisi-sfc-v3xx: add support for IRQ mode") in 5.10-rc1.

Fixed status
mainline: [de8b6e1c231a95abf95ad097b993d34b31458ec9]
stable/5.10: [e94da8aca2e78ef9ecca02eb211869eacd5504e5]
stable/5.15: [0399d7eba41d9b28f5bdd7757ec21a5b7046858d]
stable/6.1: [f19361d570c67e7e014896fa2dacd7d721bf0aa8]
stable/6.6: [d637b5118274701e8448f35953877daf04df18b4]
stable/6.7: [e4168ac25b4bd378bd7dda322d589482a136c1fd]

CVE-2024-26777: fbdev: sis: Error out if pixclock equals zero

Announce: https://lore.kernel.org/linux-cve-announce/2024040309-CVE-2024-26777-3c7c@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc2.

Fixed status
cip/4.4: [3837467fac54c0ce4cd27b3e7fe274f724d543b2]
cip/4.4-rt: [3837467fac54c0ce4cd27b3e7fe274f724d543b2]
cip/4.4-st: [3837467fac54c0ce4cd27b3e7fe274f724d543b2]
mainline: [e421946be7d9bf545147bea8419ef8239cb7ca52]
stable/4.19: [84246c35ca34207114055a87552a1c4289c8fd7e]
stable/5.10: [cd36da760bd1f78c63c7078407baf01dd724f313]
stable/5.15: [df6e2088c6f4cad539cf67cba2d6764461e798d1]
stable/5.4: [6db07619d173765bd8622d63809cbfe361f04207]
stable/6.1: [f329523f6a65c3bbce913ad35473d83a319d5d99]
stable/6.6: [99f1abc34a6dde248d2219d64aa493c76bbdd9eb]
stable/6.7: [1d11dd3ea5d039c7da089f309f39c4cd363b924b]

CVE-2024-26778: fbdev: savage: Error out if pixclock equals zero

Announce: https://lore.kernel.org/linux-cve-announce/2024040309-CVE-2024-26778-8137@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc2.

Fixed status
cip/4.4: [6172966f364e632310e95f18e67755fdd95a7dd9]
cip/4.4-rt: [6172966f364e632310e95f18e67755fdd95a7dd9]
cip/4.4-st: [6172966f364e632310e95f18e67755fdd95a7dd9]
mainline: [04e5eac8f3ab2ff52fa191c187a46d4fdbc1e288]
stable/4.19: [224453de8505aede1890f007be973925a3edf6a1]
stable/5.10: [512ee6d6041e007ef5bf200c6e388e172a2c5b24]
stable/5.15: [8c54acf33e5adaad6374bf3ec1e3aff0591cc8e1]
stable/5.4: [84dce0f6a4cc5b7bfd7242ef9290db8ac1dd77ff]
stable/6.1: [070398d32c5f3ab0e890374904ad94551c76aec4]
stable/6.6: [bc3c2e58d73b28b9a8789fca84778ee165a72d13]
stable/6.7: [a9ca4e80d23474f90841251f4ac0d941fa337a01]

CVE-2024-26779: wifi: mac80211: fix race condition on enabling fast-xmit

Announce: https://lore.kernel.org/linux-cve-announce/2024040310-CVE-2024-26779-8030@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc2.

Fixed status
cip/4.4: [16f509814b0db3baed21f39884f7c4d8b59fa91e]
cip/4.4-rt: [16f509814b0db3baed21f39884f7c4d8b59fa91e]
cip/4.4-st: [16f509814b0db3baed21f39884f7c4d8b59fa91e]
mainline: [bcbc84af1183c8cf3d1ca9b78540c2185cd85e7f]
stable/4.19: [76fad1174a0cae6fc857b9f88b261a2e4f07d587]
stable/5.10: [5ffab99e070b9f8ae0cf60c3c3602b84eee818dd]
stable/5.15: [88c18fd06608b3adee547102505d715f21075c9d]
stable/5.4: [85720b69aef177318f4a18efbcc4302228a340e5]
stable/6.1: [eb39bb548bf974acad7bd6780fe11f9e6652d696]
stable/6.6: [54b79d8786964e2f840e8a2ec4a9f9a50f3d4954]
stable/6.7: [281280276b70c822f55ce15b661f6d1d3228aaa9]

* Updated CVEs

CVE-2023-47233: Use after Free bug in brcmf_cfg80211_detach

stable 6.1, 6.6, 6.7, and 6.8 were fixed.

Fixed status
mainline: [0f7352557a35ab7888bc7831411ec8a3cbe20d78]
stable/6.1: [0b812f706fd7090be74812101114a0e165b36744]
stable/6.6: [190794848e2b9d15de92d502b6ac652806904f5a]
stable/6.7: [6678a1e7d896c00030b31491690e8ddc9a90767a]
stable/6.8: [0a7591e14a8da794d0b93b5d1c6254ccb23adacb]

CVE-2024-23307: Integer Overflow bug was found md/raid/raid5 modules

stable 6.1, 6.6, 6.7, and 6.8 were fixed.

Fixed status
mainline: [dfd2bf436709b2bccb78c2dda550dde93700efa7]
stable/6.1: [9477cfeb300823461b44223a7d5fac26a31df4fe]
stable/6.6: [8ec4a68a25a231e2303716a0aba8ff1413d47c87]
stable/6.7: [1191f9391105e49115715e55030476849f6f6da5]
stable/6.8: [83dcc4e850c69ca569e1b0f1484910e6a68b2d78]

CVE-2024-24861: Race condition bug was found in media/xc4000 device
driver in xc4000 xc4000_get_frequency()

stable 6.1, 6.6, 6.7, and 6.8 were fixed.

Fixed status
mainline: [36d503ad547d1c75758a6fcdbec2806f1b6aeb41]
stable/6.1: [09c1be4d581d3356159abcc5a8a7a6c5f1bf1e77]
stable/6.6: [dc5e4f240473b64f7b2f24424e96c92435ebd8d7]
stable/6.7: [b0864de231dece0f7226b909521bebc86105743a]
stable/6.8: [5c26122885cedcb99606cdc06a3419db7feb1e1e]

CVE-2024-26584: net: tls: handle backlogging of crypto requests

stable 6.1 was fixed.

Fixed status
mainline: [8590541473188741055d27b955db0777569438e3]
stable/6.1: [cd1bbca03f3c1d845ce274c0d0a66de8e5929f72]
stable/6.6: [13eca403876bbea3716e82cdfe6f1e6febb38754]
stable/6.7: [ab6397f072e5097f267abf5cb08a8004e6b17694]

CVE-2024-26585: tls: fix race between tx work scheduling and socket close

stable 6.1 was fixed.

Fixed status
mainline: [e01e3934a1b2d122919f73bc6ddbe1cdafc4bbdb]
stable/6.1: [196f198ca6fce04ba6ce262f5a0e4d567d7d219d]
stable/6.6: [6db22d6c7a6dc914b12c0469b94eb639b6a8a146]
stable/6.7: [e327ed60bff4a991cd7a709c47c4f0c5b4a4fd57]

CVE-2024-26642: netfilter: nf_tables: disallow anonymous set with timeout flag

stable 6.1, 6.6, and 6.7 ware fixed.

Fixed status
mainline: [16603605b667b70da974bea8216c93e7db043bf1]
stable/6.1: [72c1efe3f247a581667b7d368fff3bd9a03cd57a]
stable/6.6: [c0c2176d1814b92ea4c8e7eb7c9cd94cd99c1b12]
stable/6.7: [8e07c16695583a66e81f67ce4c46e94dece47ba7]

CVE-2024-26643: netfilter: nf_tables: mark set as dead when unbinding
anonymous set with timeout

stable 6.1, 6.6, and 6.7 ware fixed.

Fixed status
mainline: [552705a3650bbf46a22b1adedc1b04181490fc36]
stable/6.1: [406b0241d0eb598a0b330ab20ae325537d8d8163]
stable/6.6: [b2d6f9a5b1cf968f1eaa71085ceeb09c2cb276b1]
stable/6.7: [5224afbc30c3ca9ba23e752f0f138729b2c48dd8]

Currently tracking CVEs

CVE-2021-31615: Unencrypted Bluetooth Low Energy baseband links in
Bluetooth Core Specifications 4.0 through 5.2

There is no fix information.

CVE-2020-26556: kernel: malleable commitment Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26557: kernel: predictable Authvalue in Bluetooth Mesh
Provisioning Leads to MITM

No fix information.

CVE-2020-26559: kernel: Authvalue leak in Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26560: kernel: impersonation attack in Bluetooth Mesh Provisioning

No fix information.

Regards,
-- 
Masami Ichikawa
Cybertrust Japan Co., Ltd.

Email :masami.ichikawa@cybertrust.co.jp
          :masami.ichikawa@miraclelinux.com


^ permalink raw reply	[flat|nested] 33+ messages in thread

* [kernel-cve-report] New CVE entries this week
@ 2024-03-20 23:36 Masami Ichikawa
  0 siblings, 0 replies; 33+ messages in thread
From: Masami Ichikawa @ 2024-03-20 23:36 UTC (permalink / raw)
  To: cip-dev

Hi!

It's this week's CVE report.

This week reported 49 new CVEs and 11 updated CVEs.

* New CVEs

CVE-2021-47109: neighbour: allow NUD_NOARP entries to be forced GCed

Announce: https://lore.kernel.org/linux-cve-announce/2024031558-CVE-2021-47109-5bde@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 5895631 (neighbor: Improve garbage collection) in v5.0-rc1.
Older stable kernels are not affected.
Fixed in v5.13-rc7.

Fixed status
mainline: [7a6b1ab7475fd6478eeaf5c9d1163e7a18125c8f]
stable/5.10: [d17d47da59f726dc4c87caebda3a50333d7e2fd3]
stable/5.4: [d99029e6aab62aef0a0251588b2867e77e83b137]

CVE-2021-47110: x86/kvm: Disable kvmclock on all CPUs on shutdown

Announce: https://lore.kernel.org/linux-cve-announce/2024031506-CVE-2021-47110-2cb8@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v5.13-rc2.
It looks like this fix may be applied to older stable kernels.

Fixed status
mainline: [c02027b5742b5aa804ef08a4a9db433295533046]
stable/5.10: [3b0becf8b1ecf642a9edaf4c9628ffc641e490d6]
stable/5.4: [9084fe1b3572664ad276f427dce575f580c9799a]

CVE-2021-47111: xen-netback: take a reference to the RX task thread

Announce: https://lore.kernel.org/linux-cve-announce/2024031506-CVE-2021-47111-4bd0@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 2ac061c ('xen/netback: cleanup init and deinit
code') in v5.5-rc1.
Older stable kernels are not affected. It's the same as CVE-2021-28691.
Fixed in v5.13-rc6.

Fixed status
mainline: [107866a8eb0b664675a260f1ba0655010fac1e08]
stable/5.10: [6b53db8c4c14b4e7256f058d202908b54a7b85b4]

CVE-2021-47112: x86/kvm: Teardown PV features on boot CPU as well

Announce: https://lore.kernel.org/linux-cve-announce/2024031507-CVE-2021-47112-339c@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v5.13-rc2.
Linux 4.19 may be able to apply this fix.
The kvm_cpu_down_prepare() was introduced by commit 9a20ea4 ("x86/kvm:
Convert to hotplug state machine") in 4.9-rc1.
So, Linux 4.4 may not be affected.

Fixed status
mainline: [8b79feffeca28c5459458fe78676b081e87c93a4]
stable/5.10: [38b858da1c58ad46519a257764e059e663b59ff2]
stable/5.4: [7620a669111b52f224d006dea9e1e688e2d62c54]

CVE-2021-47113: btrfs: abort in rename_exchange if we fail to insert
the second ref

Announce: https://lore.kernel.org/linux-cve-announce/2024031507-CVE-2021-47113-bf29@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v5.13-rc5.
This commit log says it's for 4.9+. the btrfs_rename_exchange() is not
found in the Linux 4.4.

Fixed status
mainline: [dc09ef3562726cd520c8338c1640872a60187af5]
stable/5.10: [0df50d47d17401f9f140dfbe752a65e5d72f9932]

CVE-2021-47114: ocfs2: fix data corruption by fallocate

Announce: https://lore.kernel.org/linux-cve-announce/2024031507-CVE-2021-47114-6af8@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v5.13-rc5.
All stable kernels have been fixed.

Fixed status
cip/4.4: [624fa7baa3788dc9e57840ba5b94bc22b03cda57]
cip/4.4-rt: [624fa7baa3788dc9e57840ba5b94bc22b03cda57]
cip/4.4-st: [624fa7baa3788dc9e57840ba5b94bc22b03cda57]
mainline: [6bba4471f0cc1296fe3c2089b9e52442d3074b2e]
stable/4.19: [cec4e857ffaa8c447f51cd8ab4e72350077b6770]
stable/4.4: [624fa7baa3788dc9e57840ba5b94bc22b03cda57]
stable/5.10: [c8d5faee46242c3f33b8a71a4d7d52214785bfcc]
stable/5.4: [cc2edb99ea606a45182b5ea38cc8f4e583aa0774]

CVE-2021-47115: nfc: fix NULL ptr dereference in llcp_sock_getname()
after failed connect

Announce: https://lore.kernel.org/linux-cve-announce/2024031508-CVE-2021-47115-9715@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

This CVE was rejected.

Introduced by commit d646960 ("NFC: Initial LLCP support") in v3.3-rc1.
Fixed in v5.13-rc5.
All stable kernels have been fixed.

Fixed status
cip/4.4: [eb6875d48590d8e564092e831ff07fa384d7e477]
cip/4.4-rt: [eb6875d48590d8e564092e831ff07fa384d7e477]
cip/4.4-st: [eb6875d48590d8e564092e831ff07fa384d7e477]
mainline: [4ac06a1e013cf5fdd963317ffd3b968560f33bba]
stable/4.19: [93e4ac2a9979a9a4ecc158409ed9c3044dc0ae1f]
stable/4.4: [eb6875d48590d8e564092e831ff07fa384d7e477]
stable/5.10: [48ee0db61c8299022ec88c79ad137f290196cac2]
stable/5.4: [5d4c4b06ed9fb7a69d0b2e2a73fc73226d25ab70]

CVE-2021-47116: ext4: fix memory leak in ext4_mb_init_backend on error path.

Announce: https://lore.kernel.org/linux-cve-announce/2024031508-CVE-2021-47116-8383@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v5.13-rc5.
It seems as if commit f91436d5 ("fs/ext4: fix integer overflow in
s_log_groups_per_flex") in 5.12-rc4 introduced this bug.
The commit f91436d5 was backported to 5.10.

Fixed status
mainline: [a8867f4e3809050571c98de7a2d465aff5e4daf5]
stable/5.10: [2050c6e5b161e5e25ce3c420fef58b24fa388a49]

CVE-2021-47117: ext4: fix bug on in ext4_es_cache_extent as
ext4_split_extent_at failed

Announce: https://lore.kernel.org/linux-cve-announce/2024031508-CVE-2021-47117-5ea7@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v5.13-rc5.
All stable kernels have been fixed.

Fixed status
cip/4.4: [e33bafad30d34cfa5e9787cb099cab05e2677fcb]
cip/4.4-rt: [e33bafad30d34cfa5e9787cb099cab05e2677fcb]
cip/4.4-st: [e33bafad30d34cfa5e9787cb099cab05e2677fcb]
mainline: [082cd4ec240b8734a82a89ffb890216ac98fec68]
stable/4.19: [569496aa3776eea1ff0d49d0174ac1b7e861e107]
stable/4.4: [e33bafad30d34cfa5e9787cb099cab05e2677fcb]
stable/5.10: [d3b668b96ad3192c0581a248ae2f596cd054792a]
stable/5.4: [920697b004e49cb026e2e15fe91be065bf0741b7]

CVE-2021-47118: pid: take a reference when initializing `cad_pid`

Announce: https://lore.kernel.org/linux-cve-announce/2024031509-CVE-2021-47118-faf2@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 9ec5209 ("[PATCH] replace cad_pid by a struct
pid") in v2.6.20.16.
Fixed in v5.13-rc5.
All stable kernels have been fixed.

Fixed status
cip/4.4: [764c2e892d1fe895392aff62fb353fdce43bb529]
cip/4.4-rt: [764c2e892d1fe895392aff62fb353fdce43bb529]
cip/4.4-st: [764c2e892d1fe895392aff62fb353fdce43bb529]
mainline: [0711f0d7050b9e07c44bc159bbc64ac0a1022c7f]
stable/4.19: [d106f05432e60f9f62d456ef017687f5c73cb414]
stable/4.4: [764c2e892d1fe895392aff62fb353fdce43bb529]
stable/5.10: [7178be006d495ffb741c329012da289b62dddfe6]
stable/5.4: [2cd6eedfa6344f5ef5c3dac3aee57a39b5b46dff]

CVE-2021-47119: ext4: fix memory leak in ext4_fill_super

Announce: https://lore.kernel.org/linux-cve-announce/2024031509-CVE-2021-47119-22d3@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit ce40733 ("ext4: Check for return value from
sb_set_blocksize") in v2.6.25-rc1.
Introduced by commit ac27a0e ("ext4: initial copy of files from ext3")
in v2.6.20.16.
Fixed in v5.13-rc5.

Fixed status
mainline: [afd09b617db3786b6ef3dc43e28fe728cfea84df]
stable/5.10: [01d349a481f0591230300a9171330136f9159bcd]

CVE-2021-47120: HID: magicmouse: fix NULL-deref on disconnect

Announce: https://lore.kernel.org/linux-cve-announce/2024031510-CVE-2021-47120-c3db@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 9d7b186 ("HID: magicmouse: add support for Apple
Magic Trackpad 2") in v4.20-rc1.
This commit is not backported to 4.4 and 4.19.
Fixed in v5.13-rc5.

Fixed status
mainline: [4b4f6cecca446abcb686c6e6c451d4f1ec1a7497]
stable/5.10: [b5d013c4c76b276890135b5d32803c4c63924b77]
stable/5.4: [368c5d45a87e1bcc7f1e98e0c255c37b7b12c5d6]

CVE-2021-47121: net: caif: fix memory leak in cfusbl_device_notify

Announce: https://lore.kernel.org/linux-cve-announce/2024031510-CVE-2021-47121-13c1@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 7ad65bf ("caif: Add support for CAIF over CDC NCM
USB interface") in v3.3-rc1.
Fixed in v5.13-rc5.
All stable kernels have been fixed.

Fixed status
cip/4.4: [cc302e30a504e6b60a9ac8df7988646f46cd0294]
cip/4.4-rt: [cc302e30a504e6b60a9ac8df7988646f46cd0294]
cip/4.4-st: [cc302e30a504e6b60a9ac8df7988646f46cd0294]
mainline: [7f5d86669fa4d485523ddb1d212e0a2d90bd62bb]
stable/4.19: [9ea0ab48e755d8f29fe89eb235fb86176fdb597f]
stable/4.4: [cc302e30a504e6b60a9ac8df7988646f46cd0294]
stable/5.10: [46403c1f80b0d3f937ff9c4f5edc63bb64bc5051]
stable/5.4: [4d94f530cd24c85aede6e72b8923f371b45d6886]

CVE-2021-47122: net: caif: fix memory leak in caif_device_notify

Announce: https://lore.kernel.org/linux-cve-announce/2024031510-CVE-2021-47122-b183@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 7c18d22 ("caif: Restructure how link caif link
layer enroll") in v3.3-rc1.
Fixed in v5.13-rc5.
All stable kernels have been fixed.

Fixed status
cip/4.4: [b042e2b2039565eb8f0eb51c14fbe1ef463c8cd8]
cip/4.4-rt: [b042e2b2039565eb8f0eb51c14fbe1ef463c8cd8]
cip/4.4-st: [b042e2b2039565eb8f0eb51c14fbe1ef463c8cd8]
mainline: [b53558a950a89824938e9811eddfc8efcd94e1bb]
stable/4.19: [3be863c11cab725add9fef4237ed4e232c3fc3bb]
stable/4.4: [b042e2b2039565eb8f0eb51c14fbe1ef463c8cd8]
stable/5.10: [af2806345a37313f01b1c9f15e046745b8ee2daa]
stable/5.4: [f52f4fd67264c70cd0b4ba326962ebe12d9cba94]

CVE-2021-47123: io_uring: fix ltout double free on completion race

Announce: https://lore.kernel.org/linux-cve-announce/2024031511-CVE-2021-47123-8318@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 90cd7e4 ("io_uring: track link timeout's master
explicitly") in v5.11-rc1.
Fixed in v5.13-rc2.
All stable kernels have been fixed.

Fixed status
mainline: [447c19f3b5074409c794b350b10306e1da1ef4ba]

CVE-2021-47124: io_uring: fix link timeout refs

Announce: https://lore.kernel.org/linux-cve-announce/2024031511-CVE-2021-47124-42c9@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 9ae1f8d ("io_uring: fix inconsistent lock state")
in v5.12-rc1.
Fixed in v5.13-rc2. The io_uring feature was introduced in 5.1.

Fixed status
mainline: [a298232ee6b9a1d5d732aa497ff8be0d45b5bd82]
stable/5.10: [6f5d7a45f58d3abe3a936de1441b8d6318f978ff]

CVE-2021-47125: sch_htb: fix refcount leak in htb_parent_to_leaf_offload

Announce: https://lore.kernel.org/linux-cve-announce/2024031511-CVE-2021-47125-9c33@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit ae81feb ("sch_htb: fix null pointer dereference
on a null new_q") in v5.12-rc7.
This commit is not backported to older stable kernels.
Fixed in v5.13-rc5.

Fixed status
mainline: [944d671d5faa0d78980a3da5c0f04960ef1ad893]

CVE-2021-47126: ipv6: Fix KASAN: slab-out-of-bounds Read in
fib6_nh_flush_exceptions

Announce: https://lore.kernel.org/linux-cve-announce/2024031512-CVE-2021-47126-f717@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit f88d8ea ("ipv6: Plumb support for nexthop object
in a fib6_info") in v5.3-rc1.
Introduced by commit 706ec91 ("ipv6: Fix nexthop refcnt leak when
creating ipv6 route info") in v5.8.
These commits are not backported to 4.x kernels.
Fixed in v5.13-rc5.

Fixed status
mainline: [821bbf79fe46a8b1d18aa456e8ed0a3c208c3754]
stable/5.10: [09870235827451409ff546b073d754a19fd17e2e]
stable/5.4: [7ba7fa78a92dc410b6f93ed73075ab669c3a0b59]

CVE-2021-47127: ice: track AF_XDP ZC enabled queues in bitmap

Announce: https://lore.kernel.org/linux-cve-announce/2024031512-CVE-2021-47127-d0d6@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit c7a2190 ("ice: Remove xsk_buff_pool from VSI
structure") in v5.12-rc1.
This commit is not backportd to older stable kernels.
Fixed in v5.13-rc5.

Fixed status
mainline: [e102db780e1c14f10c70dafa7684af22a745b51d]

CVE-2021-47128: bpf, lockdown, audit: Fix buggy SELinux lockdown
permission checks

Announce: https://lore.kernel.org/linux-cve-announce/2024031512-CVE-2021-47128-bef7@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 59438b4 ("security,lockdown,selinux: implement
SELinux lockdown") in v5.6-rc1.
This commit is not backported to older stable kernels.
Fixed in v5.13-rc5.

Fixed status
mainline: [ff40e51043af63715ab413995ff46996ecf9583f]
stable/5.10: [ff5039ec75c83d2ed5b781dc7733420ee8c985fc]

CVE-2021-47129: netfilter: nft_ct: skip expectations for confirmed conntrack

Announce: https://lore.kernel.org/linux-cve-announce/2024031513-CVE-2021-47129-7ba5@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 857b460 ("netfilter: nft_ct: add ct expectations
support") in v5.3-rc1.
This commit is not backported to older stable kernels.
Fixed in v5.13-rc5.

Fixed status
mainline: [1710eb913bdcda3917f44d383c32de6bdabfc836]
stable/5.10: [5f3429c05e4028a0e241afdad856dd15dec2ffb9]
stable/5.4: [da8d31e80ff425f5a65dab7060d5c4aba749e562]

CVE-2021-47130: nvmet: fix freeing unallocated p2pmem

Announce: https://lore.kernel.org/linux-cve-announce/2024031513-CVE-2021-47130-9f71@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit c6e3f13 ("nvmet: add metadata support for block
devices") in v5.8-rc1.
This commit is not backported to older stable kernels.
Fixed in v5.13-rc5.

Fixed status
mainline: [bcd9a0797d73eeff659582f23277e7ab6e5f18f3]
stable/5.10: [c440cd080761b18a52cac20f2a42e5da1e3995af]

CVE-2021-47131: net/tls: Fix use-after-free after the TLS device goes
down and up

Announce: https://lore.kernel.org/linux-cve-announce/2024031513-CVE-2021-47131-eafc@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit e8f6979 ("net/tls: Add generic NIC offload
infrastructure") in v4.18-rc1.
This commit is not backportd to 4.4.
Fixed in v5.13-rc5.

Fixed status
mainline: [c55dcdd435aa6c6ad6ccac0a4c636d010ee367a4]
stable/5.10: [f1d4184f128dede82a59a841658ed40d4e6d3aa2]

CVE-2021-47132: mptcp: fix sk_forward_memory corruption on retransmission

Announce: https://lore.kernel.org/linux-cve-announce/2024031514-CVE-2021-47132-80b2@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 64b9cea ("mptcp: fix spurious retransmissions")
in v5.12-rc1.
This commit is not backported to older stable kernels.
Fixed in v5.13-rc5.

Fixed status
mainline: [b5941f066b4ca331db225a976dae1d6ca8cf0ae3]

CVE-2021-47133: HID: amd_sfh: Fix memory leak in amd_sfh_work

Announce: https://lore.kernel.org/linux-cve-announce/2024031514-CVE-2021-47133-1141@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 4b2c53d ("SFH:Transport Driver to add support of
AMD Sensor Fusion Hub (SFH)") in v5.11-rc1.
This commit is not backported to older stable kernels.
Fixed in v5.13-rc5.

Fixed status
mainline: [5ad755fd2b326aa2bc8910b0eb351ee6aece21b1]

CVE-2021-47134: efi/fdt: fix panic when no valid fdt found

Announce: https://lore.kernel.org/linux-cve-announce/2024031515-CVE-2021-47134-3348@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit b91540d ("RISC-V: Add EFI runtime services") in v5.10-rc1.
This commit is not backported to older stable kernels.
Fixed in v5.13-rc5.

Fixed status
mainline: [668a84c1bfb2b3fd5a10847825a854d63fac7baa]
stable/5.10: [5148066edbdc89c6fe5bc419c31a5c22e5f83bdb]

CVE-2021-47135: mt76: mt7921: fix possible AOOB issue in
mt7921_mcu_tx_rate_report

Announce: https://lore.kernel.org/linux-cve-announce/2024031515-CVE-2021-47135-2c50@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 1c099ab ("mt76: mt7921: add MCU support") in v5.12-rc1.
This commit is not backported to older stable kernels.
Fixed in v5.13-rc5.

Fixed status
mainline: [d874e6c06952382897d35bf4094193cd44ae91bd]

CVE-2023-52609: binder: fix race between mmput() and do_exit()

Announce: https://lore.kernel.org/linux-cve-announce/20240318100758.2828621-9-lee@kernel.org/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 457b9a6 ("Staging: android: add binder driver")
in v2.6.29-rc1.
This is android's driver.
Fixed in v6.8-rc1.

Fixed status
mainline: [9a9ab0d963621d9d12199df9817e66982582d5a5]
stable/4.19: [95b1d336b0642198b56836b89908d07b9a0c9608]
stable/5.10: [7e7a0d86542b0ea903006d3f42f33c4f7ead6918]
stable/5.15: [98fee5bee97ad47b527a997d5786410430d1f0e9]
stable/5.4: [252a2a5569eb9f8d16428872cc24dea1ac0bb097]
stable/6.1: [6696f76c32ff67fec26823fc2df46498e70d9bf3]
stable/6.6: [67f16bf2cc1698fd50e01ee8a2becc5a8e6d3a3e]
stable/6.7: [77d210e8db4d61d43b2d16df66b1ec46fad2ee01]

CVE-2023-52610: net/sched: act_ct: fix skb leak and crash on ooo frags

Announce: https://lore.kernel.org/linux-cve-announce/20240318100758.2828621-10-lee@kernel.org/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit b57dc7c ("net/sched: Introduce action ct") in v5.3-rc1.
Linux 4.x is not affected.
Fixed in v6.8-rc1.

Fixed status
mainline: [3f14b377d01d8357eba032b4cabc8c1149b458b6]
stable/5.15: [172ba7d46c202e679f3ccb10264c67416aaeb1c4]
stable/6.1: [0b5b831122fc3789fff75be433ba3e4dd7b779d4]
stable/6.6: [73f7da5fd124f2cda9161e2e46114915e6e82e97]
stable/6.7: [f5346df0591d10bc948761ca854b1fae6d2ef441]

CVE-2023-52611: wifi: rtw88: sdio: Honor the host max_req_size in the RX path

Announce: https://lore.kernel.org/linux-cve-announce/20240318100758.2828621-11-lee@kernel.org/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 65371a3 ("wifi: rtw88: sdio: Add HCI
implementation for SDIO based chipsets") in v6.4-rc1.
This patch is not backported to older stable kernels.
Fixed in v6.8-rc1.

Fixed status
mainline: [00384f565a91c08c4bedae167f749b093d10e3fe]
stable/6.6: [5b5ddf21b978ec315cab9d9e7e6ac7374791a8c7]
stable/6.7: [0e9ffff72a0674cd6656314dbd99cdd2123a3030]

CVE-2023-52612: crypto: scomp - fix req->dst buffer overflow

Announce: https://lore.kernel.org/linux-cve-announce/20240318100758.2828621-12-lee@kernel.org/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 1ab53a7 ("crypto: acomp - add driver-side scomp
interface") in v4.10-rc1.
Linux 4.4 is not affected.
Fixed in v6.8-rc1.

Fixed status
mainline: [744e1885922a9943458954cfea917b31064b4131]
stable/4.19: [1142d65c5b881590962ad763f94505b6dd67d2fe]
stable/5.10: [4518dc468cdd796757190515a9be7408adc8911e]
stable/5.15: [a5f2f91b3fd7387e5102060809316a0f8f0bc625]
stable/5.4: [e0e3f4a18784182cfe34e20c00eca11e78d53e76]
stable/6.1: [4df0c942d04a67df174195ad8082f6e30e7f71a5]
stable/6.6: [7d9e5bed036a7f9e2062a137e97e3c1e77fb8759]
stable/6.7: [71c6670f9f032ec67d8f4e3f8db4646bf5a62883]

CVE-2023-52613: drivers/thermal/loongson2_thermal: Fix incorrect
PTR_ERR() judgment

Announce: https://lore.kernel.org/linux-cve-announce/20240318100758.2828621-13-lee@kernel.org/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit e7e3a7c ("thermal/drivers/loongson-2: Add thermal
management support") in v6.6-rc1.
This patch is not backported to older stable kernels.
Fixed in v6.8-rc1.

Fixed status
mainline: [15ef92e9c41124ee9d88b01208364f3fe1f45f84]
stable/6.6: [70481755ed77400e783200e2d022e5fea16060ce]
stable/6.7: [6010a9fc14eb1feab5cafd84422001134fe8ec58]

CVE-2023-52614: PM / devfreq: Fix buffer overflow in trans_stat_show

Announce: https://lore.kernel.org/linux-cve-announce/20240318101458.2835626-9-lee@kernel.org/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit e552bba ("PM / devfreq: Add sysfs node for
representing frequency transition information.") in v3.8-rc1.
Fixed in v6.8-rc1.
Backporting to this fix for the following branches failed.

4.19: https://lore.kernel.org/stable/2024012637-creation-woven-808c@gregkh/
5.4: https://lore.kernel.org/stable/2024012635-corner-boondocks-1f40@gregkh/
5.10: https://lore.kernel.org/stable/2024012634-unbounded-bullfight-568f@gregkh/
5.15: https://lore.kernel.org/stable/2024012633-cornhusk-gusto-e970@gregkh/

Fixed status
mainline: [08e23d05fa6dc4fc13da0ccf09defdd4bbc92ff4]
stable/5.15: [796d3fad8c35ee9df9027899fb90ceaeb41b958f]
stable/6.1: [8a7729cda2dd276d7a3994638038fb89035b6f2c]
stable/6.6: [a979f56aa4b93579cf0e4265ae04d7e9300fd3e8]
stable/6.7: [eaef4650fa2050147ca25fd7ee43bc0082e03c87]

CVE-2023-52615: hwrng: core - Fix page fault dead lock on mmap-ed hwrng

Announce: https://lore.kernel.org/linux-cve-announce/20240318101458.2835626-10-lee@kernel.org/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 9996508 ("hwrng: core - Replace u32 in driver API
with byte array") in v2.6.33-rc1.
All stable kernels are fixed.
Fixed in v6.8-rc1.

Fixed status
cip/4.4: [02eaf55d73263373c47207ecd2a3fd85478fb8a6]
cip/4.4-rt: [02eaf55d73263373c47207ecd2a3fd85478fb8a6]
cip/4.4-st: [02eaf55d73263373c47207ecd2a3fd85478fb8a6]
mainline: [78aafb3884f6bc6636efcc1760c891c8500b9922]
stable/4.19: [eafd83b92f6c044007a3591cbd476bcf90455990]
stable/5.10: [c6a8111aacbfe7a8a70f46cc0de8eed00561693c]
stable/5.15: [26cc6d7006f922df6cc4389248032d955750b2a0]
stable/5.4: [5030d4c798863ccb266563201b341a099e8cdd48]
stable/6.1: [aa8aa16ed9adf1df05bb339d588cf485a011839e]
stable/6.6: [ecabe8cd456d3bf81e92c53b074732f3140f170d]
stable/6.7: [6822a14271786150e178869f1495cc03e74c5029]

CVE-2023-52616: crypto: lib/mpi - Fix unexpected pointer access in mpi_ec_init

Announce: https://lore.kernel.org/linux-cve-announce/20240318101458.2835626-11-lee@kernel.org/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit d58bb7e ("lib/mpi: Introduce ec implementation to
MPI library") in v5.10-rc1.
Linux 4.x is not affected.
Fixed in v6.8-rc1.

Fixed status
mainline: [ba3c5574203034781ac4231acf117da917efcd2a]
stable/5.10: [0c3687822259a7628c85cd21a3445cbe3c367165]
stable/5.15: [2bb86817b33c9d704e127f92b838035a72c315b6]
stable/6.1: [bb44477d4506e52785693a39f03cdc6a2c5e8598]
stable/6.6: [7ebf812b7019fd2d4d5a7ca45ef4bf3a6f4bda0a]
stable/6.7: [7abdfd45a650c714d5ebab564bb1b988f14d9b49]

CVE-2023-52617: PCI: switchtec: Fix stdev_release() crash after
surprise hot remove

Announce: https://lore.kernel.org/linux-cve-announce/20240318102117.2839904-7-lee@kernel.org/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc1.
Linux 4.4 doesn't have PCI_SW_SWITCHTEC feature that was introduced by
commit 080b47de ("MicroSemi Switchtec management interface driver") in
4.12-rc1.
The dma_mrpc variable is introduced by commit f7eb7b8a ("switchtec:
Add MRPC DMA mode support") in 5.0-rc1.
So, the MRPC DMA mode is not implemented in Linux 4.19 therefore Linux
4.19 seems not to be affected.

Fixed status
mainline: [df25461119d987b8c81d232cfe4411e91dcabe66]
stable/5.10: [4a5d0528cf19dbf060313dffbe047bc11c90c24c]
stable/5.15: [ff1c7e2fb9e9c3f53715fbe04d3ac47b80be7eb8]
stable/5.4: [d8c293549946ee5078ed0ab77793cec365559355]
stable/6.1: [1d83c85922647758c1f1e4806a4c5c3cf591a20a]
stable/6.6: [0233b836312e39a3c763fb53512b3fa455b473b3]
stable/6.7: [e129c7fa7070fbce57feb0bfc5eaa65eef44b693]

CVE-2023-52618: block/rnbd-srv: Check for unlikely string overflow

Announce: https://lore.kernel.org/linux-cve-announce/20240318102117.2839904-8-lee@kernel.org/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc1.
The drivers/block/rnbd/rnbd-srv.c was added by commit 2de6c8de1
("block/rnbd: server: main functionality") in 5.8-rc1.

Fixed status
mainline: [9e4bf6a08d1e127bcc4bd72557f2dfafc6bc7f41]
stable/5.10: [95bc866c11974d3e4a9d922275ea8127ff809cf7]
stable/5.15: [f6abd5e17da33eba15df2bddc93413e76c2b55f7]
stable/6.1: [af7bbdac89739e2e7380387fda598848d3b7010f]
stable/6.6: [5b9ea86e662035a886ccb5c76d56793cba618827]
stable/6.7: [a2c6206f18104fba7f887bf4dbbfe4c41adc4339]

CVE-2023-52619: pstore/ram: Fix crash when setting number of cpus to
an odd number

Announce: https://lore.kernel.org/linux-cve-announce/20240318102117.2839904-9-lee@kernel.org/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc1.
This patch can be applied to Linux 4.4.

Fixed status
mainline: [d49270a04623ce3c0afddbf3e984cb245aa48e9c]
stable/4.19: [8b69c30f4e8b69131d92096cb296dc1f217101e4]
stable/5.10: [a63e48cd835c34c38ef671d344cc029b1ea5bf10]
stable/5.15: [2a37905d47bffec61e95d99f0c1cc5dc6377956c]
stable/5.4: [e9f6ac50890104fdf8194f2865680689239d30fb]
stable/6.1: [75b0f71b26b3ad833c5c0670109c0af6e021e86a]
stable/6.6: [0593cfd321df9001142a9d2c58d4144917dff7ee]
stable/6.7: [cd40e43f870cf21726b22487a95ed223790b3542]

CVE-2024-26631: ipv6: mcast: fix data-race in ipv6_mc_down / mld_ifc_work

Announce: https://lore.kernel.org/linux-cve-announce/20240318100758.2828621-14-lee@kernel.org/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 2d9a93b ("mld: convert from timer to delayed
work") in v5.13-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc1.

Fixed status
mainline: [2e7ef287f07c74985f1bf2858bedc62bd9ebf155]
stable/5.15: [62b3387beef11738eb6ce667601a28fa089fa02c]
stable/6.1: [380540bb06bb1d1b12bdc947d1b8f56cda6b5663]
stable/6.6: [3cc283fd16fba72e2cefe3a6f48d7a36b0438900]
stable/6.7: [3bb5849675ae1d592929798a2b37ea450879c855]

CVE-2024-26632: block: Fix iterating over an empty bio with
bio_for_each_folio_all

Announce: https://lore.kernel.org/linux-cve-announce/20240318100758.2828621-15-lee@kernel.org/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 640d193 ("block: Add bio_for_each_folio_all()")
in v5.17-rc1.
This patch is not backported to older stable kernels.
Fixed in v6.8-rc1.

Fixed status
mainline: [7bed6f3d08b7af27b7015da8dc3acf2b9c1f21d7]
stable/6.1: [c6350b5cb78e9024c49eaee6fdb914ad2903a5fe]
stable/6.6: [a6bd8182137a12d22d3f2cee463271bdcb491659]
stable/6.7: [ca3ede3f5893e2d26d4dbdef1eec28a8487fafde]

CVE-2024-26633: ip6_tunnel: fix NEXTHDR_FRAGMENT handling in
ip6_tnl_parse_tlv_enc_lim()

Announce: https://lore.kernel.org/linux-cve-announce/20240318100758.2828621-16-lee@kernel.org/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit fbfa743 ("ipv6: fix ip6_tnl_parse_tlv_enc_lim()")
in v4.10-rc6.
All stable kernels are fixed.
Fixed in v6.8-rc1.

Fixed status
cip/4.4: [2a1d5c8380e863dfd2ae61cc34e87aa3e37f3800]
cip/4.4-rt: [2a1d5c8380e863dfd2ae61cc34e87aa3e37f3800]
cip/4.4-st: [2a1d5c8380e863dfd2ae61cc34e87aa3e37f3800]
mainline: [d375b98e0248980681e5e56b712026174d617198]
stable/4.19: [135414f300c5db995e2a2f3bf0f455de9d014aee]
stable/5.10: [da23bd709b46168f7dfc36055801011222b076cd]
stable/5.15: [4329426cf6b8e22b798db2331c7ef1dd2a9c748d]
stable/5.4: [3f15ba3dc14e6ee002ea01b4faddc3d49200377c]
stable/6.1: [62a1fedeb14c7ac0947ef33fadbabd35ed2400a2]
stable/6.6: [687c5d52fe53e602e76826dbd4d7af412747e183]
stable/6.7: [ba8d904c274268b18ef3dc11d3ca7b24a96cb087]

CVE-2024-26634: net: fix removing a namespace with conflicting altnames

Announce: https://lore.kernel.org/linux-cve-announce/20240318101458.2835626-12-lee@kernel.org/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 7663d52 ("net: check for altname conflicts when
changing netdev's netns") in v6.6-rc7.
This commit is backported to 6.1. Linux 5.x and 4.x are not affected.
Fixed in v6.8-rc2.

Fixed status
mainline: [d09486a04f5da0a812c26217213b89a3b1acf836]
stable/6.1: [a2232f29bf52c24f827865b3c90829c44b6c695b]
stable/6.6: [e855dded4b70d1975ee7b9fed0c700391e3c8ea6]
stable/6.7: [8072699aa9e67d1727692cfb3c347263bb627fb9]

CVE-2024-26635: llc: Drop support for ETH_P_TR_802_2.

Announce: https://lore.kernel.org/linux-cve-announce/20240318101458.2835626-13-lee@kernel.org/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 211ed86 ("net: delete all instances of special
processing for token ring") in v3.5-rc1.
All stable kernels are fixed.
Fixed in v6.8-rc2.

Fixed status
cip/4.4: [f8193f86f0c661e7aa5b8242c14635c7f215a3f8]
cip/4.4-rt: [f8193f86f0c661e7aa5b8242c14635c7f215a3f8]
cip/4.4-st: [f8193f86f0c661e7aa5b8242c14635c7f215a3f8]
mainline: [e3f9bed9bee261e3347131764e42aeedf1ffea61]
stable/4.19: [165ad1e22779685c3ed3dd349c6c4c632309cc62]
stable/5.10: [9ccdef19cf9497c2803b005369668feb91cacdfd]
stable/5.15: [c0fe2fe7a5a291dfcf6dc64301732c8d3dc6a828]
stable/5.4: [b8e8838f82f332ae80c643dbb1ca4418d0628097]
stable/6.1: [660c3053d992b68fee893a0e9ec9159228cffdc6]
stable/6.6: [f1f34a515fb1e25e85dee94f781e7869ae351fb8]
stable/6.7: [df57fc2f2abf548aa889a36ab0bdcc94a75399dc]

CVE-2024-26636: llc: make llc_ui_sendmsg() more robust against bonding changes

Announce: https://lore.kernel.org/linux-cve-announce/20240318101458.2835626-14-lee@kernel.org/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 1da177e ("Linux-2.6.12-rc2") in v2.6.12.
All stable kernels are fixed.
Fixed in v6.8-rc2.

Fixed status
cip/4.4: [4ddc8884b6d21e2830feb0fa52501220d53ebcf6]
cip/4.4-rt: [4ddc8884b6d21e2830feb0fa52501220d53ebcf6]
cip/4.4-st: [4ddc8884b6d21e2830feb0fa52501220d53ebcf6]
mainline: [dad555c816a50c6a6a8a86be1f9177673918c647]
stable/4.19: [84e9d10419f6f4f3f3cd8f9aaf44a48719aa4b1b]
stable/5.10: [04f2a74b562f3a7498be0399309669f342793d8c]
stable/5.15: [c22044270da68881074fda81a7d34812726cb249]
stable/5.4: [b643d0defcbacd7fe548bc65c3e4e6f17dc5eb2d]
stable/6.1: [6d53b813ff8b177f86f149c2f744442681f720e4]
stable/6.6: [cafd3ad3fe03ef4d6632747be9ee15dc0029db4b]
stable/6.7: [c451c008f563d56d5e676c9dcafae565fcad84bb]

CVE-2024-26637: wifi: ath11k: rely on mac80211 debugfs handling for vif

Announce: https://lore.kernel.org/linux-cve-announce/20240318101458.2835626-15-lee@kernel.org/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 0a3d898 ("wifi: mac80211: add/remove driver
debugfs entries as appropriate") in v6.7.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc2.

Fixed status
mainline: [556857aa1d0855aba02b1c63bc52b91ec63fc2cc]
stable/6.7: [aa74ce30a8a40d19a4256de4ae5322e71344a274]

CVE-2024-26638: nbd: always initialize struct msghdr completely

Announce: https://lore.kernel.org/linux-cve-announce/20240318101458.2835626-16-lee@kernel.org/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit f94fd25 ("tcp: pass back data left in socket
after receive") in v5.19-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc1.

Fixed status
mainline: [78fbb92af27d0982634116c7a31065f24d092826]
stable/6.1: [d9c54763e5cdbbd3f81868597fe8aca3c96e6387]
stable/6.6: [1960f2b534da1e6c65fb96f9e98bda773495f406]
stable/6.7: [b0028f333420a65a53a63978522db680b37379dd]

CVE-2024-26639: mm, kmsan: fix infinite recursion due to RCU critical section

Announce: https://lore.kernel.org/linux-cve-announce/20240318102117.2839904-10-lee@kernel.org/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 5ec8e8e ("mm/sparsemem: fix race in accessing
memory_section->usage") in 6.8-rc1.
This commit is backported to 5.10, 5.15, 6.1, and 6.6.
Fixed by commit f6564fce256a ("mm, kmsan: fix infinite recursion due
to RCU critical section") in 6.8-rc3.

Fixed status
mainline: [f6564fce256a3944aa1bc76cb3c40e792d97c1eb]
stable/6.1: [dc904345e3771aa01d0b8358b550802fdc6fe00b]
stable/6.6: [6335c0cdb2ea0ea02c999e04d34fd84f69fb27ff]
stable/6.7: [5a33420599fa0288792537e6872fd19cc8607ea6]

CVE-2024-26640: tcp: add sanity checks to rx zerocopy

Announce: https://lore.kernel.org/linux-cve-announce/20240318102117.2839904-11-lee@kernel.org/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 93ab6cc ("tcp: implement mmap() for zero copy
receive") in v4.18-rc1.
Linux 4.4 is not affected.
Fixed in v6.8-rc3.

Fixed status
mainline: [577e4432f3ac810049cb7e6b71f4d96ec7c6e894]
stable/5.10: [f48bf9a83b1666d934247cb58a9887d7b3127b6f]
stable/5.15: [718f446e60316bf606946f7f42367d691d21541e]
stable/6.1: [b383d4ea272fe5795877506dcce5aad1f6330e5e]
stable/6.6: [d15cc0f66884ef2bed28c7ccbb11c102aa3a0760]
stable/6.7: [1b8adcc0e2c584fec778add7777fe28e20781e60]

CVE-2024-26641: ip6_tunnel: make sure to pull inner header in __ip6_tnl_rcv()

Announce: https://lore.kernel.org/linux-cve-announce/20240318102117.2839904-12-lee@kernel.org/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 0d3c703 ("ipv6: Cleanup IPv6 tunnel receive
path") in v4.7-rc1.
Linux 4.4 is not affected.
Fixed in v6.8-rc3.

Fixed status
mainline: [8d975c15c0cd744000ca386247432d57b21f9df0]
stable/5.10: [a9bc32879a08f23cdb80a48c738017e39aea1080]
stable/5.15: [af6b5c50d47ab43e5272ad61935d0ed2e264d3f0]
stable/6.1: [d54e4da98bbfa8c257bdca94c49652d81d18a4d8]
stable/6.6: [350a6640fac4b53564ec20aa3f4a0922cb0ba5e6]
stable/6.7: [c835df3bcc14858ae9b27315dd7de76370b94f3a]

* Updated CVEs

CVE-2023-28746: Register File Data Sampling (RFDS)

stable 6.1, 6.6, 6.7, and 6.8 were fixed.

Fixed status
mainline: [e95df4ec0c0c9791941f112db699fae794b9862a,
4e42765d1be01111df0c0275bbaf1db1acef346e,
  8076fcde016c9c0e0660543e67bff86cb48a7c9c,
2a0180129d726a4b953232175857d442651b55a0]
stable/6.1: [8b5760939db9c49c03b9e19f6c485a8812f48d83,
29476fac750dddeabc3503bf9b13e05b949d7adb,
  d405b9c03f06b1b5e73ebc4f34452687022f7029,
b2e92ab17e440a97c716b701ecd897eebca11ac0]
stable/6.6: [c35ca0968de41952af2ad7d22881e4a7c6e1b145,
ddfd38558acc5b3891fd197372fedb76372da740,
  77018fb9efe50cf24e61275ee09253cf1fbb6854,
4a5b5bfea063745471af6395d22ebaea8242225e]
stable/6.7: [18867a204511d032c2a6ed083461a10905061fac,
13acf9f1df3513ea7a5170399c2a8e297e5fbdc1,
  fe5f4d14cdad934c5c92080cebd5b18189bf4ac9,
328607cf9e1fcbbc3f5521391d601306f72a5890]
stable/6.8: [056c33c67a74aec19668b927d460825f5e9aab42,
7586a7c0ba2f16ee6fe7f1ad95313775717e9f53,
  c8a1b14f43bb89a62c1471ec2931f152b37b3782,
50d33b98b1e23d1cd8743b3cac7a0ae5718b8b00]

CVE-2024-23196: NULL pointer dereference bug was found in sound/hda
device driver

Fixed in 6.5-rc1. The mainline, 5.10, 5.15, 5.4, and 6.1 were fixed.
Vulnerable function snd_hdac_regmap_sync() was introduced by commit
1a462be52 ("ALSA: hda: Manage concurrent reg access more properly") in
5.6-rc1.
This commit is not backported to 4.x so 4.19 and 4.4 are not affected.

Fixed status
mainline: [1f4a08fed450db87fbb5ff5105354158bdbe1a22]
stable/5.10: [9f9eed451176ffcac6b5ba0f6dae1a6b4a1cb0eb]
stable/5.15: [8703b26387e1fa4f8749db98d24c67617b873acb]
stable/5.4: [109f0aaa0b8838a88af9125b79579023539300a7]
stable/6.1: [cdd412b528dee6e0851c4735d6676ec138da13a4]

CVE-2024-22099: NULL pointer dereference bug and buffer overflow
vulnerabilities was found in the bluetooth subsystem

Fixed in 6.8-rc7 in the mainline.
This fix can be applied to all stable kernels.

Fixed status
mainline: [2535b848fa0f42ddff3e5255cf5e742c9b77bb26]

CVE-2024-23307: Integer Overflow bug was found md/raid/raid5 modules

Fixed in the master branch in the mainline.

Fixed status
mainline: [dfd2bf436709b2bccb78c2dda550dde93700efa7]

CVE-2024-24860: NULL pointer dereference bug was found in bluetooth
device driver in {min,max}_key_size_set()

The mainline, 5.10, 5.15, 6.1, 6.6, and 6.7 were fixed.
This bug was introduced by commit 18f8124 ("Bluetooth: Move
{min,max}_key_size debugfs ...") in 5.6-rc1.
This commit is not backported to older stable kernels.

Fixed status
mainline: [da9065caa594d19b26e1a030fd0cc27bd365d685]
stable/5.10: [394c6c0b6d9bdd7d6ebca35ca9cfbabf44c0c257]
stable/5.15: [4c71c01df8ef209e7fe22b58666cd2cf3dbafb44]
stable/6.1: [96860d9ad462db61f4eeb09934235c38eab655c4]
stable/6.6: [f56e715ef1c19c42c6aa6cb9280947dea13aab2e]
stable/6.7: [d1c6a77d6d48215ba723f910eaabdb6e60d21a37]

CVE-2024-24861: Race condition bug was found in media/xc4000 device
driver in xc4000 xc4000_get_frequency()

Fixed in the master branch in the mainline.
This bug was introduced by commit 4c07e32 ("[media] xc4000: Fix
get_frequency()") in 3.17-rc1.

Fixed status
mainline: [36d503ad547d1c75758a6fcdbec2806f1b6aeb41]

Currently tracking CVEs

CVE-2021-31615: Unencrypted Bluetooth Low Energy baseband links in
Bluetooth Core Specifications 4.0 through 5.2

There is no fix information.

CVE-2020-26556: kernel: malleable commitment Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26557: kernel: predictable Authvalue in Bluetooth Mesh
Provisioning Leads to MITM

No fix information.

CVE-2020-26559: kernel: Authvalue leak in Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26560: kernel: impersonation attack in Bluetooth Mesh Provisioning

No fix information.

Regards,
-- 
Masami Ichikawa
Cybertrust Japan Co., Ltd.

Email :masami.ichikawa@cybertrust.co.jp
          :masami.ichikawa@miraclelinux.com


^ permalink raw reply	[flat|nested] 33+ messages in thread

* [kernel-cve-report] New CVE entries this week
@ 2024-03-13 23:34 Masami Ichikawa
  0 siblings, 0 replies; 33+ messages in thread
From: Masami Ichikawa @ 2024-03-13 23:34 UTC (permalink / raw)
  To: cip-dev

Hi!

It's this week's CVE report.

This week reported 5 new CVEs and 8 updated CVEs.

* New CVEs

CVE-2023-28746: Register File Data Sampling (RFDS)

Announce: https://www.openwall.com/lists/oss-security/2024/03/12/13
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

This CVE was published by the Xen.org security team.

You can check which Intel processors are affected via Intel "Affected
Processors: Guidance for Security Issues on Intel® Processors".
(https://www.intel.com/content/www/us/en/developer/topic-technology/software-security-guidance/processors-affected-consolidated-product-cpu-model.html)

Fixed by commit e95df4ec0c0c9791941f112db699fae794b9862a,
4e42765d1be01111df0c0275bbaf1db1acef346e,
8076fcde016c9c0e0660543e67bff86cb48a7c9c, and
2a0180129d726a4b953232175857d442651b55a0 in master branch.


Fixed status
mainline: [e95df4ec0c0c9791941f112db699fae794b9862a,
4e42765d1be01111df0c0275bbaf1db1acef346e,
8076fcde016c9c0e0660543e67bff86cb48a7c9c,
2a0180129d726a4b953232175857d442651b55a0]

CVE-2024-2193: GhostRace: Speculative Race Conditions

Announce: https://www.openwall.com/lists/oss-security/2024/03/12/14
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

This CVE was published by the Xen.org security team.

According to the researcher's report
(https://www.vusec.net/projects/ghostrace/) it said that
"""
The Linux kernel developers have no immediate plans to implement our
proposed serialization of synchronization primitives due to
performance concerns. However, they confirmed the IPI storming issue
(CVE-2024-26602) and implemented an IPI rate-limiting feature
to address the CPU saturation issue by adding a synchronization mutex
on the path of sys_membarrier and avoiding its concurrent
execution on multiple cores. Unfortunately, as our experiments show
(Figure 4), hindering IPI storming primitives (i.e., 0 storming cores)
is insufficient to close the attack surface completely.
"""

Fixed status
Not fixed yet

CVE-2023-52608: firmware: arm_scmi: Check mailbox/SMT channel for consistency

Announce: https://lore.kernel.org/linux-cve-announce/20240313140155.1913910-3-lee@kernel.org/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 5c8a47a ("firmware: arm_scmi: Make scmi core
independent of the transport type") in v5.7-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc2.

Fixed status
mainline: [437a310b22244d4e0b78665c3042e5d1c0f45306]
stable/5.15: [614cc65032dcb0b64d23f5c5e338a8a04b12be5d]
stable/6.1: [7f95f6997f4fdd17abec3200cae45420a5489350]
stable/6.6: [9b5e1b93c83ee5fc9f5d7bd2d45b421bd87774a2]
stable/6.7: [12dc4217f16551d6dee9cbefc23fdb5659558cda]

CVE-2024-26629: nfsd: fix RELEASE_LOCKOWNER

Announce: https://lore.kernel.org/linux-cve-announce/20240313140155.1913910-4-lee@kernel.org/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit ce3c4ad ("NFSD: Fix possible sleep during
nfsd4_release_lockowner()") in v5.19-rc1.
This commit is backported to 4.4, 4.19, 5.4, 5.10, and 5.15. All
stable kernels are affected.
Fixed in v6.8-rc2.

Fixed status
mainline: [edcf9725150e42beeca42d085149f4c88fa97afd]
stable/6.1: [e4cf8941664cae2f89f0189c29fe2ce8c6be0d03]
stable/6.6: [b7d2eee1f53899b53f069bba3a59a419fc3d331b]
stable/6.7: [8f5b860de87039b007e84a28a5eefc888154e098]

CVE-2024-26630: mm: cachestat: fix folio read-after-free in cache walk

Announce: https://lore.kernel.org/linux-cve-announce/20240313155037.1968072-2-lee@kernel.org/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit cf264e1 ("cachestat: implement cachestat
syscall") in v6.5-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc7.

Fixed status
mainline: [3a75cb05d53f4a6823a32deb078de1366954a804]
stable/6.6: [ba60fdf75e89ea762bb617be578dc47f27655117]
stable/6.7: [fe7e008e0ce728252e4ec652cceebcc62211657c]


* Updated CVEs

CVE-2023-6356: NULL pointer dereference in nvmet_tcp_build_iovec

The mainline and all stable kernels are fixed. Linux 4.x is not affected.

Fixed status
mainline: [efa56305908ba20de2104f1b8508c6a7401833be]
stable/5.10: [f775f2621c2ac5cc3a0b3a64665dad4fb146e510]
stable/5.15: [4cb3cf7177ae3666be7fb27d4ad4d72a295fb02d]
stable/5.4: [ee5e7632e981673f42a50ade25e71e612e543d9d]
stable/6.1: [2871aa407007f6f531fae181ad252486e022df42]
stable/6.6: [24e05760186dc070d3db190ca61efdbce23afc88]
stable/6.7: [70154e8d015c9b4fb56c1a2ef1fc8b83d45c7f68]

CVE-2023-6536: NULL pointer dereference in __nvmet_req_complete

The mainline and all stable kernels are fixed. Linux 4.x is not affected.

Fixed status
mainline: [0849a5441358cef02586fb2d60f707c0db195628]
stable/5.10: [39669fae69f302961d89f38d969c6fcc1d07eb02]
stable/5.15: [0613a2fbdf8d32c3f8f1e62d704e92251a100795]
stable/5.4: [9638beb4e10ac116c6a4fc13315e9c3608055ac0]
stable/6.1: [83ccd15717ee2b6143df72df39685f0c832e3451]
stable/6.6: [2f00fd8d50a7d5eedc85e62efdc1a29213168998]
stable/6.7: [c32d355f507fa81cf23aaa4dd4150e696cb8ebaf]

CVE-2024-0841: hugetlbfs: Null pointer dereference in
hugetlbfs_fill_super function

The mainline and all stable kernels are fixed. Linux 4.x is not affected.

Fixed status
mainline: [79d72c68c58784a3e1cd2378669d51bfd0cb7498]
stable/5.10: [80d852299987a8037be145a94f41874228f1a773]
stable/5.15: [22850c9950a4e43a67299755d11498f3292d02ff]
stable/5.4: [1dde8ef4b7a749ae1bc73617c91775631d167557]
stable/6.1: [2e2c07104b4904aed1389a59b25799b95a85b5b9]
stable/6.6: [13c5a9fb07105557a1fa9efdb4f23d7ef30b7274]
stable/6.7: [ec78418801ef7b0c22cd6a30145ec480dd48db39]

Currently tracking CVEs

CVE-2021-31615: Unencrypted Bluetooth Low Energy baseband links in
Bluetooth Core Specifications 4.0 through 5.2

There is no fix information.

CVE-2020-26556: kernel: malleable commitment Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26557: kernel: predictable Authvalue in Bluetooth Mesh
Provisioning Leads to MITM

No fix information.

CVE-2020-26559: kernel: Authvalue leak in Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26560: kernel: impersonation attack in Bluetooth Mesh Provisioning

No fix information.

Regards,
-- 
Masami Ichikawa
Cybertrust Japan Co., Ltd.

Email :masami.ichikawa@cybertrust.co.jp
          :masami.ichikawa@miraclelinux.com


^ permalink raw reply	[flat|nested] 33+ messages in thread

* [kernel-cve-report] New CVE entries this week
@ 2024-03-07  3:08 Masami Ichikawa
  0 siblings, 0 replies; 33+ messages in thread
From: Masami Ichikawa @ 2024-03-07  3:08 UTC (permalink / raw)
  To: cip-dev

Hi!

It's this week's CVE report.

This week reported 277 new CVEs and 10 updated CVEs.

* New CVEs

CVE-2020-36779: i2c: stm32f7: fix reference leak when pm_runtime_get_sync fails

Announce: https://lore.kernel.org/linux-cve-announce/2024022819-CVE-2020-36779-9f1e@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit ea6dd25 ("i2c: stm32f7: add PM_SLEEP
suspend/resume support") in 5.6-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [2c662660ce2bd3b09dae21a9a9ac9395e1e6c00b]
stable/5.10: [c323b270a52a26aa8038a4d1fd9a850904a41166]

CVE-2020-36778: i2c: xiic: fix reference leak when pm_runtime_get_sync fails

Announce: https://lore.kernel.org/linux-cve-announce/2024022817-CVE-2020-36778-48a5@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 10b1700 ("i2c: xiic: Fix the clocking across bind
unbind") in 5.6-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [a85c5c7a3aa8041777ff691400b4046e56149fd3]
stable/5.10: [c977426db644ba476938125597947979e8aba725]

CVE-2020-36780: i2c: sprd: fix reference leak when pm_runtime_get_sync fails

Announce: https://lore.kernel.org/linux-cve-announce/2024022820-CVE-2020-36780-9637@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 8b9ec07 ("i2c: Add Spreadtrum I2C controller
driver") in 4.14-rc1.
Linux 4.4 is not affected.
Fixed in 5.13-rc1.

Fixed status
mainline: [a85c5c7a3aa8041777ff691400b4046e56149fd3]
stable/5.10: [c977426db644ba476938125597947979e8aba725]

CVE-2020-36781: i2c: imx: fix reference leak when pm_runtime_get_sync fails

Announce: https://lore.kernel.org/linux-cve-announce/2024022820-CVE-2020-36781-d70c@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 3a5ee18 ("i2c: imx: implement master_xfer_atomic
callback") in 5.7-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.7-rc1.

Fixed status
mainline: [47ff617217ca6a13194fcb35c6c3a0c57c080693]
stable/5.10: [3a0cdd336d92c429b51a79bf4f64b17eafa0325d]

CVE-2020-36782: i2c: imx-lpi2c: fix reference leak when
pm_runtime_get_sync fails

Announce: https://lore.kernel.org/linux-cve-announce/2024022820-CVE-2020-36782-e7d8@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 13d6eb2 ("i2c: imx-lpi2c: add runtime pm
support") in 4.16-rc1.
Linux 4.4 is not affected.
Fixed in 5.13-rc1.

Fixed status
mainline: [278e5bbdb9a94fa063c0f9bcde2479d0b8042462]
stable/5.10: [cc49d206414240483bb93ffa3d80243e6a776916]
stable/5.4: [815859cb1d2302e74f11bf6894bceace9ca9eb4a]

CVE-2020-36783: i2c: img-scb: fix reference leak when pm_runtime_get_sync fails

Announce: https://lore.kernel.org/linux-cve-announce/2024022820-CVE-2020-36783-8372@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 93222bd ("i2c: img-scb: Add runtime PM") in 4.15-rc1.
Linux 4.4 is not affected.
Fixed in 5.13-rc1.

Fixed status
mainline: [223125e37af8a641ea4a09747a6a52172fc4b903]
stable/5.10: [e80ae8bde41266d3b8bf012460b6593851766006]
stable/5.4: [4734c4b1d9573c9d20bbc46cf37dde095ee011b8]

CVE-2020-36784: i2c: cadence: fix reference leak when pm_runtime_get_sync fails

Announce: https://lore.kernel.org/linux-cve-announce/2024022821-CVE-2020-36784-a266@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 7fa3232 ("i2c: cadence: Move to sensible power
management") in 4.5-rc1.
Linux 4.4 is not affected.
Fixed in 5.13-rc1.

Fixed status
mainline: [23ceb8462dc6f4b4decdb5536a7e5fc477cdf0b6]
stable/5.10: [30410519328c94367e561fd878e5f0d3a0303585]

CVE-2020-36785: media: atomisp: Fix use after free in
atomisp_alloc_css_stat_bufs()

Announce: https://lore.kernel.org/linux-cve-announce/2024022821-CVE-2020-36784-a266@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit ad85094 ("Revert "media: staging: atomisp: Remove
driver"") in 5.8-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [ba11bbf303fafb33989e95473e409f6ab412b18d]
stable/5.10: [d218c7a0284f6b92a7b82d2e19706e18663b4193]

CVE-2020-36787: media: aspeed: fix clock handling logic

Announce: https://lore.kernel.org/linux-cve-announce/2024022821-CVE-2020-36787-7efe@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit d2b4387 ("media: platform: Add Aspeed Video
Engine driver") in 5.0-rc1 and
d3d04f6 ("clk: Add support for AST2600 SoC") 5.4-rc1.
Linux 4.x is not affected.
Fixed in 5.13-rc1.

Fixed status
mainline: [3536169f8531c2c5b153921dc7d1ac9fd570cda7]
stable/5.10: [a59d01384c80a8a4392665802df57c3df20055f5]
stable/5.4: [1dc1d30ac101bb8335d9852de2107af60c2580e7]

CVE-2021-46984: kyber: fix out of bounds access when preempted

Announce: https://lore.kernel.org/linux-cve-announce/2024022824-CVE-2021-46984-e55e@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit a608884 ("block: kyber: make kyber more friendly
with merging") in 4.18-rc1.
Linux 4.4 is not affected.
Fixed in 5.13-rc2.

Fixed status
mainline: [efed9a3337e341bd0989161b97453b52567bc59d]
stable/5.10: [54dbe2d2c1fcabf650c7a8b747601da355cd7f9f]
stable/5.4: [0b6b4b90b74c27bea968c214d820ba4254b903a5]

CVE-2021-46985: ACPI: scan: Fix a memory leak in an error handling path

Announce: https://lore.kernel.org/linux-cve-announce/2024022824-CVE-2021-46985-4dad@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit eb50aaf ("ACPI: scan: Use unique number for
instance_no") in 5.12-rc5.
This commit is backported to 5.10, 5.4, and 4.19. Linux 4.4 is not affected.
Fixed in 5.13-rc2.

Fixed status
mainline: [0c8bd174f0fc131bc9dfab35cd8784f59045da87]
stable/4.19: [69cc821e89ce572884548ac54c4f80eec7a837a5]
stable/5.10: [e2381174daeae0ca35eddffef02dcc8de8c1ef8a]
stable/5.4: [dafd4c0b5e835db020cff11c74b4af9493a58e72]

CVE-2021-46986: usb: dwc3: gadget: Free gadget structure only after
freeing endpoints

Announce: https://lore.kernel.org/linux-cve-announce/2024022824-CVE-2021-46986-1d6e@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit e81a701 ("usb: dwc3: allocate gadget structure
dynamically") in 5.10-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc2.

Fixed status
mainline: [bb9c74a5bd1462499fe5ccb1e3c5ac40dcfa9139]
stable/5.10: [1ea775021282d90e1d08d696b7ab54aa75d688e5]

CVE-2021-46987: btrfs: fix deadlock when cloning inline extents and
using qgroups

Announce: https://lore.kernel.org/linux-cve-announce/2024022825-CVE-2021-46987-f73f@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit c6887cd ("Btrfs: don't do nocow check unless we
have to") in 5.9-rc1.
This commit is backported to 5.4. Linux 4.x is not affected.
Fixed in 5.9-rc1.

Fixed status
mainline: [f9baa501b4fd6962257853d46ddffbc21f27e344]

CVE-2021-46988: userfaultfd: release page in error path to avoid BUG_ON

Announce: https://lore.kernel.org/linux-cve-announce/2024022825-CVE-2021-46988-ae47@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit cb658a4 ("userfaultfd: shmem: avoid leaking
blocks and used blocks in UFFDIO_COPY") in 4.11-rc4.
Linux 4.4 is not affected.
Fixed in 5.13-rc2.

Fixed status
mainline: [7ed9d238c7dbb1fdb63ad96a6184985151b0171c]
stable/4.19: [07c9b834c97d0fa3402fb7f3f3b32df370a6ff1f]
stable/5.10: [140cfd9980124aecb6c03ef2e69c72d0548744de]
stable/5.4: [b3f1731c6d7fbc1ebe3ed8eff6d6bec56d76ff43]

CVE-2021-46989: hfsplus: prevent corruption in shrinking truncate

Announce: https://lore.kernel.org/linux-cve-announce/2024022825-CVE-2021-46989-8377@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 31651c6 ("hfsplus: avoid deadlock on file
truncation") in 4.19-rc1.
Linux 4.4 is not affected.
Fixed in 5.13-rc2.

Fixed status
mainline: [c3187cf32216313fb316084efac4dab3a8459b1d]
stable/4.19: [52dde855663e5db824af51db39b5757d2ef3e28a]
stable/5.10: [adbd8a2a8cc05d9e501f93e5c95c59307874cc99]
stable/5.4: [c451a6bafb5f422197d31536f82116aed132b72c]

CVE-2021-46990: powerpc/64s: Fix crashes when toggling entry flush barrier

Announce: https://lore.kernel.org/linux-cve-announce/2024022825-CVE-2021-46990-5ab1@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 5f68718 ("netfilter: nf_tables: GC transaction
API to avoid race with control plane") in 6.5-rc6.
Fixed in 6.7.

Fixed status
cip/4.4: [8382b15864e5014261b4f36c2aa89723612ee058]
cip/4.4-rt: [8382b15864e5014261b4f36c2aa89723612ee058]
cip/4.4-st: [8382b15864e5014261b4f36c2aa89723612ee058]
mainline: [aec86b052df6541cc97c5fca44e5934cbea4963b]
stable/4.19: [2db22ba4e0e103f00e0512e0ecce36ac78c644f8]
stable/5.10: [d2e3590ca39ccfd8a5a46d8c7f095cb6c7b9ae92]
stable/5.4: [0b4eb172cc12dc102cd0ad013e53ee4463db9508]

CVE-2021-46991: i40e: Fix use-after-free in i40e_client_subtask()

Announce: https://lore.kernel.org/linux-cve-announce/2024022826-CVE-2021-46991-3c16@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 7b0b1a6 ("i40e: Disable iWARP VSI PETCP_ENA flag
on netdev down events") in 4.16-rc1.
Linux 4.4 is not affected.
Fixed in 5.13-rc1.

Fixed status
mainline: [38318f23a7ef86a8b1862e5e8078c4de121960c3]
stable/4.19: [c1322eaeb8af0d8985b5cc5fa759140fa0e57b84]
stable/5.10: [829a713450b8fb127cbabfc1244c1d8179ec5107]
stable/5.4: [d718c15a2bf9ae082d5ae4d177fb19ef23cb4132]

CVE-2021-46992: netfilter: nftables: avoid overflows in nft_hash_buckets()

Announce: https://lore.kernel.org/linux-cve-announce/2024022826-CVE-2021-46991-3c16@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 0ed6389 ("netfilter: nf_tables: rename set
implementations") in 4.9-rc1.
Linux 4.4 is not affected.
Fixed in 5.13-rc1.

Fixed status
mainline: [a54754ec9891830ba548e2010c889e3c8146e449]
stable/4.19: [efcd730ddd6f25578bd31bfe703e593e2421d708]
stable/5.10: [72b49dd116ca00a46a11d5a4d8d7987f05ed9cd7]
stable/5.4: [c77e2ef18167ad334e27610ced9a7f6af5ec1787]

CVE-2021-46993: sched: Fix out-of-bound access in uclamp

Announce: https://lore.kernel.org/linux-cve-announce/2024022826-CVE-2021-46993-da22@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 69842cb ("sched/uclamp: Add CPU's clamp buckets
refcounting") in 5.3-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [6d2f8909a5fabb73fe2a63918117943986c39b6c]
stable/5.10: [f7347c85490b92dd144fa1fba9e1eca501656ab3]
stable/5.4: [687f523c134b7f0bd040ee1230f6d17990d54172]

CVE-2021-46976: drm/i915: Fix crash in auto_retire

Announce: https://lore.kernel.org/linux-cve-announce/2024022822-CVE-2021-46976-1dd4@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 229007e ("drm/i915: Wrap i915_active in a simple
kreffed struct") in 5.8-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc2.

Fixed status
mainline: [402be8a101190969fc7ff122d07e262df86e132b]
stable/5.10: [805c990a9c54b9451d3daff640b850909c31ab9d]

CVE-2021-46994: can: mcp251x: fix resume from sleep before interface
was brought up

Announce: https://lore.kernel.org/linux-cve-announce/2024022826-CVE-2021-46994-4722@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 8ce8c0a ("can: mcp251x: only reset hardware as
required") in 5.5-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [03c427147b2d3e503af258711af4fc792b89b0af]
stable/5.10: [eecb4df8ec9f896b19ee05bfa632ac6c1dcd8f21]

CVE-2021-46995: can: mcp251xfd: mcp251xfd_probe(): fix an error
pointer dereference in probe

Announce: https://lore.kernel.org/linux-cve-announce/2024022827-CVE-2021-46995-6757@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit cf8ee6d ("can: mcp251xfd: mcp251xfd_probe(): use
dev_err_probe() to simplify error handling") in 5.12-rc1-dontuse
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [4cc7faa406975b460aa674606291dea197c1210c]

CVE-2021-46996: netfilter: nftables: Fix a memleak from userdata error
path in new objects

Announce: https://lore.kernel.org/linux-cve-announce/2024022827-CVE-2021-46996-0af4@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit b131c96 ("netfilter: nf_tables: add userdata
support for nft_object") in 5.10-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [85dfd816fabfc16e71786eda0a33a7046688b5b0]
stable/5.10: [2c784a500f5edd337258b0fdb2f31bc9abde1a23]

CVE-2021-46997: arm64: entry: always set GIC_PRIO_PSR_I_SET during entry

Announce: https://lore.kernel.org/linux-cve-announce/2024022827-CVE-2021-46997-a93c@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 2352904 ("arm64: entry: fix non-NMI user<->kernel
transitions") in 5.10-rc7 and
7cd1ea1 ("arm64: entry: fix non-NMI kernel<->kernel transitions") in
5.10-rc7 and
f0cd5ac ("arm64: entry: fix NMI {user, kernel}->kernel transitions")
in 5.10-rc7 and
2a9b3e6 ("arm64: entry: fix EL1 debug transitions") in 5.10-rc7.
These commits are not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [4d6a38da8e79e94cbd1344aa90876f0f805db705]
stable/5.10: [51524fa8b5f7b879ba569227738375d283b79382]

CVE-2021-46998: ethernet:enic: Fix a use after free bug in enic_hard_start_xmit

Announce: https://lore.kernel.org/linux-cve-announce/2024022827-CVE-2021-46998-eda2@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit fb7516d ("enic: add sw timestamp support") in 4.16-rc1.
These commits are not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [643001b47adc844ae33510c4bb93c236667008a3]
stable/4.19: [25a87b1f566b5eb2af2857a928f0e2310d900976]
stable/5.10: [7afdd6aba95c8a526038e7abe283eeac3e4320f1]
stable/5.4: [f7f6f07774091a6ddd98500b85386c3c6afb30d3]

CVE-2021-46999: sctp: do asoc update earlier in sctp_sf_do_dupcook_a

Announce: https://lore.kernel.org/linux-cve-announce/2024022828-CVE-2021-46999-d408@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 145cb2f ("sctp: Fix bundling of SHUTDOWN with
COOKIE-ACK") in 5.7-rc3.
This commit is backported to 5.4 and 4.19. Linux 4.4 is not affected.
Fixed in 5.13-rc1.

Fixed status
mainline: [35b4f24415c854cd718ccdf38dbea6297f010aae]
stable/4.19: [d624f2991b977821375fbd56c91b0c91d456a697]
stable/5.10: [f01988ecf3654f805282dce2d3bb9afe68d2691e]
stable/5.4: [b1b31948c0af44628e43353828453461bb74098f]

CVE-2021-47000: ceph: fix inode leak on getattr error in __fh_to_dentry

Announce: https://lore.kernel.org/linux-cve-announce/2024022828-CVE-2021-47000-981a@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 878dabb ("ceph: don't return -ESTALE if there's
still an open file") in 5.8-rc1.
This commit is backported to 5.4 Linux 4.x is not affected.
Fixed in 5.13-rc1.

Fixed status
mainline: [1775c7ddacfcea29051c67409087578f8f4d751b]
stable/5.10: [bf45c9fe99aa8003d2703f1bd353f956dea47e40]
stable/5.4: [2ad8af2b70e986284050213230428b823b950a38]

CVE-2021-47001: xprtrdma: Fix cwnd update ordering

Announce: https://lore.kernel.org/linux-cve-announce/2024022828-CVE-2021-47001-0e51@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 2ae50ad ("xprtrdma: Close window between waking
RPC senders and posting Receives") in 5.5-rc.
This commit is backported to 5.4. Linux 4.x is not affected.
Fixed in 5.13-rc1.

Fixed status
mainline: [35d8b10a25884050bb3b0149b62c3818ec59f77c]
stable/5.10: [eddae8be7944096419c2ae29477a45f767d0fcd4]

CVE-2021-47002: SUNRPC: Fix null pointer dereference in svc_rqst_free()

Announce: https://lore.kernel.org/linux-cve-announce/2024022828-CVE-2021-47002-3946@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 5191955 ("SUNRPC: Prepare for xdr_stream-style
decoding on the server-side") in 5.11-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [b9f83ffaa0c096b4c832a43964fe6bff3acffe10]

CVE-2021-47003: dmaengine: idxd: Fix potential null dereference on
pointer status

Announce: https://lore.kernel.org/linux-cve-announce/2024022829-CVE-2021-47003-12d7@gregkh/T/#u

Introduced by commit 89e3bec ("dmaengine: idxd: check device state
before issue command") in 5.11.
This commit is backported to 5.10. Linux 5.4 and 4.x are not affected.
Fixed in 5.13-rc1.

Fixed status
mainline: [28ac8e03c43dfc6a703aa420d18222540b801120]
stable/5.10: [5756f757c72501ef1a16f5f63f940623044180e9]

CVE-2021-46977: KVM: VMX: Disable preemption when probing user return MSRs

https://lore.kernel.org/linux-cve-announce/2024022822-CVE-2021-46977-76be@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 4be5341 ("KVM: VMX: Initialize vmx->guest_msrs[]
right after allocation") in 5.5-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc2.

Fixed status
mainline: [5104d7ffcf24749939bea7fdb5378d186473f890]
stable/5.10: [31f29749ee970c251b3a7e5b914108425940d089]

CVE-2021-47004: f2fs: fix to avoid touching checkpointed data in get_victim()

Announce: https://lore.kernel.org/linux-cve-announce/2024022829-CVE-2021-47004-8544@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 4354994 ("f2fs: checkpoint disabling") in 4.20-rc1 and
093749e ("f2fs: support age threshold based garbage collection")  5.10-rc1.
These commits are not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [61461fc921b756ae16e64243f72af2bfc2e620db]
stable/5.10: [105155a8146ddb54c119d8318964eef3859d109d]

CVE-2021-47005: PCI: endpoint: Fix NULL pointer dereference for ->get_features()

Announce: https://lore.kernel.org/linux-cve-announce/2024022829-CVE-2021-47005-8f88@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 2c04c5b ("PCI: pci-epf-test: Use
pci_epc_get_features() to get EPC features") in 5.1-rc1.
This commit is backported to cip/4.19 and cip/4.19-rt. stable/4.19 and
4.4 are not affected.
Fixed in 5.13-rc1.

Fixed status
mainline: [6613bc2301ba291a1c5a90e1dc24cf3edf223c03]
stable/5.10: [bbed83d7060e07a5d309104d25a00f0a24441428]

CVE-2021-47006: ARM: 9064/1: hw_breakpoint: Do not directly check the
event's overflow_handler hook

Announce: https://lore.kernel.org/linux-cve-announce/2024022829-CVE-2021-47006-3312@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 1879445 ("perf/core: Set event's default
::overflow_handler()") in 4.7-rc1.
Linux 4.4 is not affected.
Fixed in 5.13-rc1.

Fixed status
mainline: [a506bd5756290821a4314f502b4bafc2afcf5260]
stable/4.19: [a9938d6d78a238d6ab8de57a4d3dcf77adceb9bb]
stable/5.10: [630146203108bf6b8934eec0dfdb3e46dcb917de]
stable/5.4: [3ed8832aeaa9a37b0fc386bb72ff604352567c80]

CVE-2021-47007: f2fs: fix panic during f2fs_resize_fs()

Announce: https://lore.kernel.org/linux-cve-announce/2024022830-CVE-2021-47007-4d53@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit b4b1006 ("f2fs: refactor resize_fs to avoid meta
updates in progress") in 5.8-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [3ab0598e6d860ef49d029943ba80f627c15c15d6]
stable/5.10: [1c20a4896409f5ca1c770e1880c33d0a28a8b10f]

CVE-2021-47008: KVM: SVM: Make sure GHCB is mapped before updating

Announce: https://lore.kernel.org/linux-cve-announce/2024022830-CVE-2021-47008-3dc3@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit f1c6366 ("KVM: SVM: Add required changes to
support intercepts under SEV-ES") in 5.11-rc1 and
647daca ("KVM: SVM: Add support for booting APs in an SEV-ES guest")
in 5.11-rc3.
These commits are not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [a3ba26ecfb569f4aa3f867e80c02aa65f20aadad]

CVE-2021-46978: KVM: nVMX: Always make an attempt to map eVMCS after migration

Announce: https://lore.kernel.org/linux-cve-announce/2024022822-CVE-2021-46978-3516@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit f2c7ef3 ("KVM: nSVM: cancel
KVM_REQ_GET_NESTED_STATE_PAGES on nested vmexit") in 5.11-rc3.
This commit is backported to 5.10. Linux 5.4 and 4.x are not affected.
Fixed in 5.13-rc2.

Fixed status
mainline: [f5c7e8425f18fdb9bdb7d13340651d7876890329]
stable/5.10: [c8bf64e3fb77cc19bad146fbe26651985b117194]

CVE-2021-46979: iio: core: fix ioctl handlers removal

Announce: https://lore.kernel.org/linux-cve-announce/2024022823-CVE-2021-46979-de90@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 8dedcc3 ("iio: core: centralize ioctl() calls to
the main chardev") in 5.11-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc2.

Fixed status
mainline: [901f84de0e16bde10a72d7eb2f2eb73fcde8fa1a]

CVE-2021-46980: usb: typec: ucsi: Retrieve all the PDOs instead of
just the first 4

Announce: https://lore.kernel.org/linux-cve-announce/2024022823-CVE-2021-46980-adda@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 992a60e ("usb: typec: ucsi: register with
power_supply class") in 5.8-rc1 and
4dbc6a4 ("usb: typec: ucsi: save power data objects in PD mode") in 5.8-rc1.
These commits are not backported to older stable kernels.
Fixed in 5.13-rc2.

Fixed status
mainline: [1f4642b72be79757f050924a9b9673b6a02034bc]
stable/5.10: [e5366bea0277425e1868ba20eeb27c879d5a6e2d]

CVE-2021-46981: nbd: Fix NULL pointer in flush_workqueue

Announce: https://lore.kernel.org/linux-cve-announce/2024022823-CVE-2021-46981-0fb9@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit e9e006f ("nbd: fix max number of supported devs")
in 5.4-rc1.
This commit is backported to 4.19. Linux 4.4 is not affected.
Fixed in 5.13-rc2.

Fixed status
mainline: [79ebe9110fa458d58f1fceb078e2068d7ad37390]
stable/5.10: [cde4b55cfb24522dcbba80bbdb0c082303e76c43]
stable/5.4: [1c4962df938891af9ab4775f5224ef8601764107]

CVE-2021-46982: f2fs: compress: fix race condition of overwrite vs truncate

Announce: https://lore.kernel.org/linux-cve-announce/2024022823-CVE-2021-46982-5134@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 4c8ff70 ("f2fs: support data compression") in 5.6-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc2.

Fixed status
mainline: [a949dc5f2c5cfe0c910b664650f45371254c0744]
stable/5.10: [5639b73fd3bc6fc8ca72e3a9ac15aacaabd7ebff]

CVE-2021-46983: nvmet-rdma: Fix NULL deref when SEND is completed with error

Announce: https://lore.kernel.org/linux-cve-announce/2024022824-CVE-2021-46983-f808@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit ca0f1a8 ("nvmet-rdma: use new shared CQ
mechanism") in 5.9-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc2.

Fixed status
mainline: [8cc365f9559b86802afc0208389f5c8d46b4ad61]
stable/5.10: [64f3410c7bfc389b1a58611d0799f4a36ce4b6b5]

CVE-2020-36786: media: [next] staging: media: atomisp: fix memory leak
of object flash

Announce: https://lore.kernel.org/linux-cve-announce/2024022821-CVE-2020-36786-fa2b@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 9289cdf ("staging: media: atomisp: Convert to
GPIO descriptors") in 5.10-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [6045b01dd0e3cd3759eafe7f290ed04c957500b1]
stable/5.10: [cc4cc2fb5aaf9adb83c02211eb13b16cfcb7ba64]

CVE-2021-47010: net: Only allow init netns to set default tcp cong to
a restricted algo

Announce: https://lore.kernel.org/linux-cve-announce/2024022830-CVE-2021-47010-6853@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 6670e15 ("tcp: Namespace-ify
sysctl_tcp_default_congestion_control") in 4.15-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [8d432592f30fcc34ef5a10aac4887b4897884493]
stable/4.19: [992de06308d9a9584d59b96d294ac676f924e437]
stable/5.10: [6c1ea8bee75df8fe2184a50fcd0f70bf82986f42]
stable/5.4: [9884f745108f7d25b189bbcd6754e284fb29ab68]

CVE-2021-47021: mt76: mt7915: fix memleak when mt7915_unregister_device()

Announce: https://lore.kernel.org/linux-cve-announce/2024022833-CVE-2021-47021-6cbb@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit f285dfb ("mt76: mt7915: reset token when
mac_reset happens") in 5.12-rc1-dontuse.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [e9d32af478cfc3744a45245c0b126738af4b3ac4]

CVE-2021-47022: mt76: mt7615: fix memleak when mt7615_unregister_device()

Announce: https://lore.kernel.org/linux-cve-announce/2024022833-CVE-2021-47022-402e@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit a6275e9 ("mt76: mt7615: reset token when
mac_reset happens") in 5.12-rc1-dontuse.
This commit is backported to 5.10. Linux 4.19 and 4.4 are not affected.
Fixed in 5.13-rc1.

Fixed status
mainline: [8ab31da7b89f71c4c2defcca989fab7b42f87d71]
stable/5.10: [4fa28c807da54c1d720b3cc12e48eb9bea1e2c8f]

CVE-2021-47023: net: marvell: prestera: fix port event handling on init

Announce: https://lore.kernel.org/linux-cve-announce/2024022833-CVE-2021-47023-118c@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 501ef30 ("net: marvell: prestera: Add driver for
Prestera family ASIC devices") in 5.10-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [333980481b99edb24ebd5d1a53af70a15d9146de]
stable/5.10: [0ce6052802be2cb61a57b753e41301339c88c839]

CVE-2021-47024: vsock/virtio: free queued packets when closing socket

Announce: https://lore.kernel.org/linux-cve-announce/2024022833-CVE-2021-47024-c116@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit ac03046 ("vsock/virtio: free packets during the
socket release") in 5.2-rc2.
This commit is backported to 4.19. Linux 4.4 is not affected.
Fixed in 5.13-rc1.

Fixed status
mainline: [8432b8114957235f42e070a16118a7f750de9d39]
stable/5.10: [b605673b523fe33abeafb2136759bcbc9c1e6ebf]

CVE-2021-47025: iommu/mediatek: Always enable the clk on resume

Announce: https://lore.kernel.org/linux-cve-announce/2024022834-CVE-2021-47025-cbd5@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit c0b5758 ("iommu/mediatek: Add power-domain
operation") in 5.12-rc1dontuse.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [b34ea31fe013569d42b7e8681ef3f717f77c5b72]

CVE-2021-47026: RDMA/rtrs-clt: destroy sysfs after removing session
from active list

Announce: https://lore.kernel.org/linux-cve-announce/2024022834-CVE-2021-47026-4e19@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 6a98d71 ("RDMA/rtrs: client: main functionality")
in 5.8-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [7f4a8592ff29f19c5a2ca549d0973821319afaad]
stable/5.10: [b64415c6b3476cf9fa4d0aea3807065b8403a937]

CVE-2021-47027: mt76: mt7921: fix kernel crash when the firmware fails
to download

Announce: https://lore.kernel.org/linux-cve-announce/2024022834-CVE-2021-47027-4a56@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 5c14a5f ("mt76: mt7921: introduce mt7921e
support") in 5.12-rc1dontuse.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [e230f0c44f011f3270680a506b19b7e84c5e8923]

CVE-2021-47028: mt76: mt7915: fix txrate reporting

Announce: https://lore.kernel.org/linux-cve-announce/2024022834-CVE-2021-47028-3a13@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit e57b790 ("mt76: add mac80211 driver for MT7915
PCIe-based chipsets") in 5.8-rc1 and
e4c5ead ("mt76: mt7915: rename mt7915_mcu_get_rate_info to
mt7915_mcu_get_tx_rate") in 5.11-rc1.
These commits are not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [f43b941fd61003659a3f0e039595e5e525917aa8]

CVE-2021-47029: mt76: connac: fix kernel warning adding monitor interface

Announce: https://lore.kernel.org/linux-cve-announce/2024022835-CVE-2021-47029-2c85@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit d0e274a ("mt76: mt76_connac: create mcu library")
in 5.12-rc1dontuse.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [c996f0346e40e3b1ac2ebaf0681df898fb157f60]

CVE-2021-47030: mt76: mt7615: fix memory leak in mt7615_coredump_work

Announce: https://lore.kernel.org/linux-cve-announce/2024022835-CVE-2021-47030-d1f6@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit d2bf795 ("mt76: mt7663: introduce coredump
support") in 5.12-rc1dontuse.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [49cc85059a2cb656f96ff3693f891e8fe8f669a9]

CVE-2021-47011: mm: memcontrol: slab: fix obtain a reference to a freeing memcg

Announce: https://lore.kernel.org/linux-cve-announce/2024022831-CVE-2021-47011-5b75@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 3de7d4f ("mm: memcg/slab: optimize objcg stock
draining") in 5.11-rc5.
This commit is backported to 5.10. Linux 5.4 and 4.x are not affected.
Fixed in 5.13-rc1.

Fixed status
mainline: [9f38f03ae8d5f57371b71aa6b4275765b65454fd]
stable/5.10: [31df8bc4d3feca9f9c6b2cd06fd64a111ae1a0e6]

CVE-2021-47031: mt76: mt7921: fix memory leak in mt7921_coredump_work

Announce: https://lore.kernel.org/linux-cve-announce/2024022835-CVE-2021-47031-75a5@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 1c099ab ("mt76: mt7921: add MCU support") in
5.12-rc1dontuse.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [782b3e86ea970e899f8e723db9f64708a15ca30e]

CVE-2021-47032: mt76: mt7915: fix tx skb dma unmap

Announce: https://lore.kernel.org/linux-cve-announce/2024022835-CVE-2021-47032-b4df@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 27d5c52 ("mt76: fix double DMA unmap of the first
buffer on 7615/7915") in 5.10-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [7dcf3c04f0aca746517a77433b33d40868ca4749]
stable/5.10: [4e7914ce23306b28d377ec395e00e5fde0e6f96e]

CVE-2021-47033: mt76: mt7615: fix tx skb dma unmap

Announce: https://lore.kernel.org/linux-cve-announce/2024022836-CVE-2021-47033-4d0d@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 27d5c52 ("mt76: fix double DMA unmap of the first
buffer on 7615/7915") in 5.10-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [ebee7885bb12a8fe2c2f9bac87dbd87a05b645f9]
stable/5.10: [75bc5f779a7664d1fc19cb915039439c6e58bb94]

CVE-2021-47034: powerpc/64s: Fix pte update for kernel memory on radix

Announce: https://lore.kernel.org/linux-cve-announce/2024022836-CVE-2021-47034-0851@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit f1cb8f9 ("powerpc/64s/radix: avoid ptesync after
set_pte and ptep_set_access_flags") in 4.18-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [b8b2f37cf632434456182e9002d63cbc4cccc50c]
stable/4.19: [b3d5d0983388d6c4fb35f7d722556d5595f167a7]
stable/5.10: [84c0762633f2a7ac8399e6b97d3b9bb8e6e1d50f]
stable/5.4: [73f9dccb29e4f82574bec2765c0090cdb0404301]

CVE-2021-47035: iommu/vt-d: Remove WO permissions on second-level paging entries

Announce: https://lore.kernel.org/linux-cve-announce/2024022836-CVE-2021-47035-e152@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit b802d07 ("iommu/vt-d: Use iova over first level")
in 5.6-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [eea53c5816889ee8b64544fa2e9311a81184ff9c]
stable/5.10: [89bd620798704a8805fc9db0d71d7f812cf5b3d2]

CVE-2021-47036: udp: skip L4 aggregation for UDP tunnel packets

Announce: https://lore.kernel.org/linux-cve-announce/2024022837-CVE-2021-47036-cd49@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 9fd1ff5 ("udp: Support UDP fraglist GRO/GSO.") in
5.6-rc1 and
3670706 ("udp: allow forwarding of plain (non-fraglisted) UDP GRO
packets") in 5.12-rc1-dontuse.
These commits are not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [18f25dc399901426dff61e676ba603ff52c666f7]

CVE-2021-47037: ASoC: q6afe-clocks: fix reprobing of the driver

Announce: https://lore.kernel.org/linux-cve-announce/2024022837-CVE-2021-47037-d130@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 520a1c3 ("ASoC: q6afe-clocks: add q6afe clock
controller") in 5.10-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [96fadf7e8ff49fdb74754801228942b67c3eeebd]

CVE-2021-47038: Bluetooth: avoid deadlock between hci_dev->lock and socket lock

Announce: https://lore.kernel.org/linux-cve-announce/2024022837-CVE-2021-47038-bfcf@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit eab2404 ("Bluetooth: Add BT_PHY socket option") in 5.7-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [17486960d79b900c45e0bb8fbcac0262848582ba]
stable/5.10: [7cc0ba67883c6c8d3bddb283f56c167fc837a555]

CVE-2021-47039: ataflop: potential out of bounds in do_format()

Announce: https://lore.kernel.org/linux-cve-announce/2024022837-CVE-2021-47039-638f@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit bf9c053 ("ataflop: use a separate gendisk for
each media format") in 5.11-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [1ffec389a6431782a8a28805830b6fae9bf00af1]

CVE-2021-47040: io_uring: fix overflows checks in provide buffers

Announce: https://lore.kernel.org/linux-cve-announce/2024022838-CVE-2021-47040-8722@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit efe68c1 ("io_uring: validate the full range of
provided buffers for access") in 5.8-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [38134ada0ceea3e848fe993263c0ff6207fd46e7]
stable/5.10: [cbbc13b115b8f18e0a714d89f87fbdc499acfe2d]

CVE-2021-47012: RDMA/siw: Fix a use after free in siw_alloc_mr

Announce: https://lore.kernel.org/linux-cve-announce/2024022831-CVE-2021-47012-73c5@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 2251334 ("rdma/siw: application buffer
management") in 5.3-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [3093ee182f01689b89e9f8797b321603e5de4f63]
stable/5.10: [608a4b90ece039940e9425ee2b39c8beff27e00c]
stable/5.4: [30b9e92d0b5e5d5dc1101ab856c17009537cbca4]

CVE-2021-47041: nvmet-tcp: fix incorrect locking in state_change sk callback

Announce: https://lore.kernel.org/linux-cve-announce/2024022838-CVE-2021-47041-de92@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 872d26a ("nvmet-tcp: add NVMe over TCP target
driver") in 5.0-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [b5332a9f3f3d884a1b646ce155e664cc558c1722]
stable/5.10: [60ade0d56b06537a28884745059b3801c78e03bc]
stable/5.4: [999d606a820c36ae9b9e9611360c8b3d8d4bb777]

CVE-2021-47042: drm/amd/display: Free local data after use

Announce: https://lore.kernel.org/linux-cve-announce/2024022838-CVE-2021-47042-142d@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 3a00c04 ("drm/amd/display/dc/core/dc_link: Move
some local data from the stack to the heap") in 5.12-rc1-dontuse.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [616cf23b6cf40ad6f03ffbddfa1b6c4eb68d8ae1]

CVE-2021-47043: media: venus: core: Fix some resource leaks in the
error path of 'venus_probe()'

Announce: https://lore.kernel.org/linux-cve-announce/2024022838-CVE-2021-47043-cb3c@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 32f0a6d ("media: venus: Use on-chip interconnect
API") in 5.5-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [5a465c5391a856a0c1e9554964d660676c35d1b2]
stable/5.10: [00b68a7478343afdf83f30c43e64db5296057030]

CVE-2021-47044: sched/fair: Fix shift-out-of-bounds in load_balance()

Announce: https://lore.kernel.org/linux-cve-announce/2024022839-CVE-2021-47044-2e16@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 5a7f555 ("sched/fair: Relax constraint on task's
load during load balance") in 5.10-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [39a2a6eb5c9b66ea7c8055026303b3aa681b49a5]
stable/5.10: [80862cbf76c2646f709a57c4517aefe0b094c774]

CVE-2021-47045: scsi: lpfc: Fix null pointer dereference in lpfc_prep_els_iocb()

Announce: https://lore.kernel.org/linux-cve-announce/2024022839-CVE-2021-47045-7363@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 4430f7f ("scsi: lpfc: Rework locations of ndlp
reference taking") in 5.11-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [8dd1c125f7f838abad009b64bff5f0a11afe3cb6]

CVE-2021-47046: drm/amd/display: Fix off by one in hdmi_14_process_transaction()

Announce: https://lore.kernel.org/linux-cve-announce/2024022839-CVE-2021-47046-3ffe@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit in 4c283fd ("drm/amd/display: Add HDCP module") in 5.5-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [8e6fafd5a22e7a2eb216f5510db7aab54cc545c1]
stable/5.10: [403c4528e5887af3deb9838cb77a557631d1e138]

CVE-2021-47047: spi: spi-zynqmp-gqspi: return -ENOMEM if dma_map_single fails

Announce: https://lore.kernel.org/linux-cve-announce/2024022839-CVE-2021-47047-4c75@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 1c26372 ("spi: spi-zynqmp-gqspi: Update driver to
use spi-mem framework") in 5.10-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [126bdb606fd2802454e6048caef1be3e25dd121e]
stable/5.10: [5980a3b9c933408bc22b0e349b78c3ebd7cbf880]

CVE-2021-47013: net:emac/emac-mac: Fix a use after free in emac_mac_tx_buf_send

Announce: https://lore.kernel.org/linux-cve-announce/2024022831-CVE-2021-47013-034a@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit b9b17de ("net: emac: emac gigabit ethernet
controller driver") in 4.9-r1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [6d72e7c767acbbdd44ebc7d89c6690b405b32b57]
stable/4.19: [16d8c44be52e3650917736d45f5904384a9da834]
stable/5.10: [9dc373f74097edd0e35f3393d6248eda8d1ba99d]
stable/5.4: [55fcdd1258faaecca74b91b88cc0921f9edd775d]

CVE-2021-47014: net/sched: act_ct: fix wild memory access when
clearing fragments

Announce: https://lore.kernel.org/linux-cve-announce/2024022831-CVE-2021-47014-ffc7@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit in ae372cb ("net/sched: act_ct: fix restore the
qdisc_skb_cb after defrag") in 5.8-rc7 and
7baf242 ("net/sched: cls_flower add CT_FLAGS_INVALID flag support") in
5.12-rc1-dontuse.
These commits are not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [f77bd544a6bbe69aa50d9ed09f13494cf36ff806]

CVE-2021-47015: bnxt_en: Fix RX consumer index logic in the error path

Announce: https://lore.kernel.org/linux-cve-announce/2024022832-CVE-2021-47015-c2ae@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit a1b0e4e ("bnxt_en: Improve RX consumer index
validity check.") in 5.1-rc5.
This commit is backported to 4.19. Linux 4.4 is not affected.
Fixed in 5.13-rc1.

Fixed status
mainline: [bbd6f0a948139970f4a615dff189d9a503681a39]
stable/5.10: [4fcaad2b7dac3f16704f8118c7e481024ddbd3ed]
stable/5.4: [b1523e4ba293b2a32d9fabaf70c1dcaa6e3e2847]

CVE-2021-47017: ath10k: Fix a use after free in ath10k_htc_send_bundle

Announce: https://lore.kernel.org/linux-cve-announce/2024022832-CVE-2021-47017-c3e8@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit c833451 ("ath10k: add htt TX bundle for sdio") in 5.8-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [8392df5d7e0b6a7d21440da1fc259f9938f4dec3]
stable/5.10: [8bb054fb336f4250002fff4e0b075221c05c3c65]

CVE-2021-47018: powerpc/64: Fix the definition of the fixmap area

Announce: https://lore.kernel.org/linux-cve-announce/2024022832-CVE-2021-47018-f631@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 265c349 ("powerpc: Add support for
GENERIC_EARLY_IOREMAP") in 5.5-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [9ccba66d4d2aff9a3909aa77d57ea8b7cc166f3c]
stable/5.10: [4b9fb2c9039a206d37f215936a4d5bee7b1bf9cd]

CVE-2021-47019: mt76: mt7921: fix possible invalid register access

Announce: https://lore.kernel.org/linux-cve-announce/2024022832-CVE-2021-47019-9b9a@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit ffa1bf9 ("mt76: mt7921: introduce PM support") in
5.12-rc1-dontuse.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [fe3fccde8870764ba3e60610774bd7bc9f8faeff]

CVE-2021-47009: KEYS: trusted: Fix memory leak on object td

Announce: https://lore.kernel.org/linux-cve-announce/2024022830-CVE-2021-47009-3f56@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 5df16ca ("KEYS: trusted: Fix incorrect handling
of tpm_get_random()") in 5.12-rc1-dontuse.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc2.

Fixed status
mainline: [83a775d5f9bfda95b1c295f95a3a041a40c7f321]
stable/5.10: [31c9a4b24d86cbb36ff0d7a085725a3b4f0138c8]

CVE-2021-47049: Drivers: hv: vmbus: Use after free in __vmbus_open()

Announce: https://lore.kernel.org/linux-cve-announce/2024022840-CVE-2021-47049-5cc6@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 6f3d791 ("Drivers: hv: vmbus: Fix rescind
handling issues") in 4.14-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [3e9bf43f7f7a46f21ec071cb47be92d0874c48da]
stable/5.10: [d5c7b42c9f56ca46b286daa537d181bd7f69214f]

CVE-2021-47050: memory: renesas-rpc-if: fix possible NULL pointer
dereference of resource

Announce: https://lore.kernel.org/linux-cve-announce/2024022840-CVE-2021-47050-5ba5@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit ca7d8b9 ("memory: add Renesas RPC-IF driver") in 5.9-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [59e27d7c94aa02da039b000d33c304c179395801]
stable/5.10: [71bcc1b4a1743534d8abdcb57ff912e6bc390438]

CVE-2021-47051: spi: fsl-lpspi: Fix PM reference leak in
lpspi_prepare_xfer_hardware()

Announce: https://lore.kernel.org/linux-cve-announce/2024022840-CVE-2021-47051-cf30@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 944c01a ("spi: lpspi: enable runtime pm for
lpspi") in 5.2-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [a03675497970a93fcf25d81d9d92a59c2d7377a7]
stable/5.10: [ce02e58ddf8658a4c3bed2296f32a5873b3f7cce]
stable/5.4: [4a01ad002d2e03c399af536562693752af7c81b1]

CVE-2021-47052: crypto: sa2ul - Fix memory leak of rxd

Announce: https://lore.kernel.org/linux-cve-announce/2024022841-CVE-2021-47052-3cca@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 00c9211 ("crypto: sa2ul - Fix DMA mapping API
usage") in 5.10-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [854b7737199848a91f6adfa0a03cf6f0c46c86e8]
stable/5.10: [0e596b3734649041ed77edc86a23c0442bbe062b]

CVE-2021-47053: crypto: sun8i-ss - Fix memory leak of pad

Announce: https://lore.kernel.org/linux-cve-announce/2024022841-CVE-2021-47053-c68d@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit d9b4541 ("crypto: sun8i-ss - support hash
algorithms") in 5.10-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [50274b01ac1689b1a3f6bc4b5b3dbf361a55dd3a]
stable/5.10: [2c67a9333da9d0a3b87310e0d116b7c9070c7b00]

CVE-2021-47048: spi: spi-zynqmp-gqspi: fix use-after-free in zynqmp_qspi_exec_op

Announce: https://lore.kernel.org/linux-cve-announce/2024022840-CVE-2021-47048-8586@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 1c26372 ("spi: spi-zynqmp-gqspi: Update driver to
use spi-mem framework") in 5.10rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [a2c5bedb2d55dd27c642c7b9fb6886d7ad7bdb58]
stable/5.10: [1231279389b5e638bc3b66b9741c94077aed4b5a]

CVE-2021-46959: spi: Fix use-after-free with devm_spi_alloc_*

Announce: https://lore.kernel.org/linux-cve-announce/2024022916-CVE-2021-46959-f517@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 5e844cc ("spi: Introduce device-managed SPI
controller allocation") in 5.10-rc5.
This commit is backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
cip/4.4: [62bb2c7f2411a0045c24831f11ecacfc35610815]
cip/4.4-rt: [62bb2c7f2411a0045c24831f11ecacfc35610815]
cip/4.4-st: [62bb2c7f2411a0045c24831f11ecacfc35610815]
mainline: [794aaf01444d4e765e2b067cba01cc69c1c68ed9]
stable/4.19: [28a5529068c51cdf0295ab1e11a99a3a909a03e4]
stable/5.10: [c7fabe372a9031acd00498bc718ce27c253abfd1]
stable/5.4: [001c8e83646ad3b847b18f6ac55a54367d917d74]

CVE-2021-47016: m68k: mvme147,mvme16x: Don''t wipe PCC timer config bits

Announce: https://lore.kernel.org/linux-cve-announce/2024022919-CVE-2021-47016-320d@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 7529b90 ("m68k: mvme147: Handle timer counter
overflow") in 5.2-rc1 and
19999a8 ("m68k: mvme16x: Handle timer counter overflow") in 5.2-rc1.
These commits are not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [43262178c043032e7c42d00de44c818ba05f9967]
stable/5.10: [1dfb26df15fc7036a74221d43de7427f74293dae]
stable/5.4: [f6a90818a32058fca62cda3a2027a6a2364e1878]

CVE-2021-47020: oundwire: stream: fix memory leak in stream config error path

Announce: https://lore.kernel.org/linux-cve-announce/2024022920-CVE-2021-47020-78d9@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 89e5905 ("soundwire: Add support for SoundWire
stream management") in 4.18-rc1.
This commit is not backported to older kernels.
Fixed 5.13-rc1.

Fixed status
mainline: [48f17f96a81763c7c8bf5500460a359b9939359f]
stable/4.19: [342260fe821047c3d515e3d28085d73fbdce3e80]
stable/5.10: [7c468deae306d0cbbd539408c26cfec04c66159a]
stable/5.4: [870533403ffa28ff63e173045fc5369365642002]

CVE-2021-47054: bus: qcom: Put child node before return

Announce: https://lore.kernel.org/linux-cve-announce/2024022950-CVE-2021-47054-c994@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 335a127 ("bus: qcom: add EBI2 driver") in 4.9-rc1.
This commit is not backported to older kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [ac6ad7c2a862d682bb584a4bc904d89fa7721af8]
stable/4.19: [a399dd80e697a02cfb23e2fc09b87849994043d9]
stable/5.10: [00f6abd3509b1d70d0ab0fbe65ce5685cebed8be]
stable/5.4: [3a76ec28824c01b57aa1f0927841d75e4f167cb8]

CVE-2021-47055: mtd: require write permissions for locking and badblock ioctls

Announce: https://lore.kernel.org/linux-cve-announce/2024022950-CVE-2021-47055-6927@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit f7e6b19 ("mtd: properly check all write ioctls
for permissions") in 5.9-rc1.
This commit is backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
cip/4.4: [f4d28d8b9b0e7c4ae04214b8d7e0b0466ec6bcaf]
cip/4.4-rt: [f4d28d8b9b0e7c4ae04214b8d7e0b0466ec6bcaf]
cip/4.4-st: [f4d28d8b9b0e7c4ae04214b8d7e0b0466ec6bcaf]
mainline: [1e97743fd180981bef5f01402342bb54bf1c6366]
stable/4.19: [75ed985bd6c8ac1d4e673e93ea9d96c9908c1d37]
stable/5.10: [7b6552719c0ccbbea29dde4be141da54fdb5877e]
stable/5.4: [5880afefe0cb9b2d5e801816acd58bfe91a96981]

CVE-2021-47056: crypto: qat - ADF_STATUS_PF_RUNNING should be set
after adf_dev_init

https://lore.kernel.org/linux-cve-announce/2024022950-CVE-2021-47056-c2b3@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 25c6ffb ("crypto: qat - check if PF is running")
in 4.7-rc1.
Linux 4.4 is not affected.
Fixed in 5.13-rc1.

Fixed status
mainline: [8609f5cfdc872fc3a462efa6a3eca5cb1e2f6446]
stable/4.19: [09d16cee6285d37cc76311c29add6d97a7e4acda]
stable/5.10: [1f50392650ae794a1aea41c213c6a3e1c824413c]
stable/5.4: [05ec8192ee4bfdf2a8894a68350dac9f1a155fa6]

CVE-2021-47057: crypto: sun8i-ss - Fix memory leak of object d when
dma_iv fails to map

Announce: https://lore.kernel.org/linux-cve-announce/2024022951-CVE-2021-47057-01fa@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit ac2614d ("crypto: sun8i-ss - Add support for the
PRNG") in 5.10-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [98b5ef3e97b16eaeeedb936f8bda3594ff84a70e]
stable/5.10: [617ec35ed51f731a593ae7274228ef2cfc9cb781]

CVE-2021-47058: crypto: sun8i-ss - fix result memory leak on error path

Announce: https://lore.kernel.org/linux-cve-announce/2024022951-CVE-2021-47058-3130@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit cffa4b2 ("regmap: debugfs: Fix a memory leak when
calling regmap_attach_dev") in 5.11-rc3.
This commit is backported to 5.10, 5.4, and 4.19. Linux 4.4 is not affected.
Fixed in 5.13-rc1.

Fixed status
mainline: [e41a962f82e7afb5b1ee644f48ad0b3aee656268]
stable/4.19: [2dc1554d5f0fdaf47cc5bea442b84b9226fea867]
stable/5.10: [eb949f891226c012138ffd9df90d1e509f428ae6]
stable/5.4: [d8897f7b2283a500666c85ef06e820df38ed7b52]

CVE-2021-47060: KVM: Stop looking for coalesced MMIO zones if the bus
is destroyed

Announce: https://lore.kernel.org/linux-cve-announce/2024022952-CVE-2021-47060-d2ce@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit f658866 ("KVM: fix memory leak in
kvm_io_bus_unregister_dev()") in 5.9-rc5.
This commit is backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [5d3c4c79384af06e3c8e25b7770b6247496b4417]
stable/5.10: [2a20592baff59c5351c5200ec667e1a2aa22af85]
stable/5.4: [7d1bc32d6477ff96a32695ea4be8144e4513ab2d]

CVE-2021-47061: KVM: Destroy I/O bus devices on unregister failure
_after_ sync''ing SRCU

Announce: https://lore.kernel.org/linux-cve-announce/2024022952-CVE-2021-47061-6fea@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit in f658866 ("KVM: fix memory leak in
kvm_io_bus_unregister_dev()") in 4.11-rc5.
This commit is backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [2ee3757424be7c1cd1d0bbfa6db29a7edd82a250]
stable/5.10: [03c6cccedd3913006744faa252a4da5145299343]

CVE-2021-47062: KVM: SVM: Use online_vcpus, not created_vcpus, to
iterate over vCPUs

Announce: https://lore.kernel.org/linux-cve-announce/2024022953-CVE-2021-47062-ed39@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit ad73109 ("KVM: SVM: Provide support to launch and
run an SEV-ES guest") in 5.11-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [c36b16d29f3af5f32fc1b2a3401bf48f71cabee1]

CVE-2021-47063: drm: bridge/panel: Cleanup connector on bridge detach

Announce: https://lore.kernel.org/linux-cve-announce/2024022953-CVE-2021-47063-2f50@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 13dfc05 ("drm/bridge: Refactor out the panel
wrapper from the lvds-encoder bridge.") in 4.13-rc1.
Linux 4.4 is not affected.
Fixed in 5.13-rc1.

Fixed status
mainline: [4d906839d321c2efbf3fed4bc31ffd9ff55b75c0]
stable/5.10: [ce450934a00cf896e648fde08d0bd1426653d7a2]

CVE-2021-47064: mt76: fix potential DMA mapping leak

Announce: https://lore.kernel.org/linux-cve-announce/2024022954-CVE-2021-47064-f220@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 27d5c52 ("mt76: fix double DMA unmap of the first
buffer on 7615/7915") in 5.10-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [b4403cee6400c5f679e9c4a82b91d61aa961eccf]
stable/5.10: [9fa26701cd1fc4d932d431971efc5746325bdfce]

CVE-2021-47065: rtw88: Fix array overrun in rtw_get_tx_power_params()

Announce: https://lore.kernel.org/linux-cve-announce/2024022954-CVE-2021-47065-be1d@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit fa6dfe6 ("rtw88: resolve order of tx power
setting routines") in 5.3-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [2ff25985ea9ccc6c9af2c77b0b49045adcc62e0e]
stable/5.10: [95fb153c6027924cda3422120169d1890737f3a0]
stable/5.4: [6b5aa0cf321c25f41e09a61c83ee4dc7ab9549cb]

CVE-2021-47066: async_xor: increase src_offs when dropping destination page

Announce: https://lore.kernel.org/linux-cve-announce/2024022954-CVE-2021-47066-02e0@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 29bcff7 ("md/raid5: add new xor function to
support different page offset") in 5.10-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [ceaf2966ab082bbc4d26516f97b3ca8a676e2af8]
stable/5.10: [cab2e8e5997b592fdb7d02cf2387b4b8e3057174]

CVE-2021-47067: soc/tegra: regulators: Fix locking up when
voltage-spread is out of range

Announce: https://lore.kernel.org/linux-cve-announce/2024022955-CVE-2021-47067-8104@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 7838074 ("soc/tegra: regulators: Add regulators
coupler for Tegra30") in 5.5-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [ef85bb582c41524e9e68dfdbde48e519dac4ab3d]
stable/5.10: [a1ad124c836816fac8bd5e461d36eaf33cee4e24]

CVE-2021-47068: net/nfc: fix use-after-free llcp_sock_bind/connect

Announce: https://lore.kernel.org/linux-cve-announce/2024022955-CVE-2021-47068-a416@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit c33b1cc ("nfc: fix refcount leak in
llcp_sock_bind()") in 5.12-rc7.
This commit is backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
cip/4.4: [26157c82ba756767b2bd66d28a71b1bc454447f6]
cip/4.4-rt: [26157c82ba756767b2bd66d28a71b1bc454447f6]
cip/4.4-st: [26157c82ba756767b2bd66d28a71b1bc454447f6]
mainline: [c61760e6940dd4039a7f5e84a6afc9cdbf4d82b6]
stable/4.19: [48fba458fe54cc2a980a05c13e6c19b8b2cfb610]
stable/5.10: [6b7021ed36dabf29e56842e3408781cd3b82ef6e]
stable/5.4: [e32352070bcac22be6ed8ab635debc280bb65b8c]

CVE-2023-52476: perf/x86/lbr: Filter vsyscall addresses

Announce: https://lore.kernel.org/linux-cve-announce/2024022921-CVE-2023-52476-e307@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.
I found similar code in following files but not sure these are
vulnerable or not.

5.10: https://elixir.bootlin.com/linux/v5.10.210/source/arch/x86/events/intel/lbr.c#L1228
5.4: https://elixir.bootlin.com/linux/v5.4.269/source/arch/x86/events/intel/lbr.c#L878
4.19: https://elixir.bootlin.com/linux/v4.19.307/source/arch/x86/events/intel/lbr.c#L867
4.4: https://elixir.bootlin.com/linux/v4.4.302/source/arch/x86/kernel/cpu/perf_event_intel_lbr.c#L694

Fixed in 6.6-rc6.

Fixed status
mainline: [e53899771a02f798d436655efbd9d4b46c0f9265]
stable/5.15: [403d201d1fd144cb249836dafb222f6375871c6c]
stable/6.1: [3863989497652488a50f00e96de4331e5efabc6c]

CVE-2023-52479: ksmbd: fix uaf in smb20_oplock_break_ack

Announce: https://lore.kernel.org/linux-cve-announce/2024022922-CVE-2023-52479-fc87@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined. The ksmbd is introduced in 5.15
so prior to 5.15 kernels are not affected.
Fixed in 6.6-rc5.

Fixed status
mainline: [c69813471a1ec081a0b9bf0c6bd7e8afd818afce]
stable/5.15: [694e13732e830cbbfedb562e57f28644927c33fd]
stable/6.1: [8226ffc759ea59f10067b9acdf7f94bae1c69930]

CVE-2023-52480: ksmbd: fix race condition between session lookup and expire

Announce: https://lore.kernel.org/linux-cve-announce/2024022922-CVE-2023-52480-ff7f@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined. The ksmbd is introduced in 5.15
so prior to 5.15 kernels are not affected.
Fixed in 6.6-rc5.

Fixed status
mainline: [53ff5cf89142b978b1a5ca8dc4d4425e6a09745f]
stable/5.15: [c77fd3e25a51ac92b0f1b347a96eff6a0b4f066f]
stable/6.1: [a2ca5fd3dbcc665e1169044fa0c9e3eba779202b]

CVE-2023-52481: arm64: errata: Add Cortex-A520 speculative
unprivileged load workaround

Announce: https://lore.kernel.org/linux-cve-announce/2024022922-CVE-2023-52481-99a8@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.
Fixed in 6.6-rc5.

Fixed status
mainline: [471470bc7052d28ce125901877dd10e4c048e513]
stable/6.1: [6e3ae2927b432a3b7c8374f14dbc1bd9ebe4372c]

CVE-2023-52482: x86/srso: Add SRSO mitigation for Hygon processors

Announce: https://lore.kernel.org/linux-cve-announce/2024022922-CVE-2023-52482-9375@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.
Fixed in 6.6-rc4.

Fixed status
mainline: [a5ef7d68cea1344cf524f04981c2b3f80bedbb0d]
stable/5.15: [f090a8b4d2e3ec6f318d6fdab243a2edc5a8cc37]
stable/6.1: [6ce2f297a7168274547d0b5aea6c7c16268b8a96]

CVE-2023-52484: iommu/arm-smmu-v3: Fix soft lockup triggered by
arm_smmu_mm_invalidate_range

Announce: https://lore.kernel.org/linux-cve-announce/2024022923-CVE-2023-52484-3635@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.
Fixed in 6.6-rc5.

Fixed status
mainline: [d5afb4b47e13161b3f33904d45110f9e6463bad6]
stable/5.15: [f5a604757aa8e37ea9c7011dc9da54fa1b30f29b]
stable/6.1: [f90f4c562003ac3d3b135c5a40a5383313f27264]

CVE-2023-52485: drm/amd/display: Wake DMCUB before sending a command

Announce: https://lore.kernel.org/linux-cve-announce/20240229150009.1525992-2-lee@kernel.org/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.
Fixed in 6.8-rc1.

Fixed status
mainline: [8892780834ae294bc3697c7d0e056d7743900b39]
stable/6.7: [303197775a97416b62d4da69280d0c120a20e009]

CVE-2023-52486: drm: Don''t unref the same fb many times by mistake
due to deadlock handling

Announce: https://lore.kernel.org/linux-cve-announce/20240229155245.1571576-27-lee@kernel.org/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined. It looks as if it's good to backport to 4.4
(https://elixir.bootlin.com/linux/v4.4.302/source/drivers/gpu/drm/drm_crtc.c#L5329).
Fixed in 6.8-rc1.

Fixed status
mainline: [cb4daf271302d71a6b9a7c01bd0b6d76febd8f0c]
stable/4.19: [376e21a9e4c2c63ee5d8d3aa74be5082c3882229]
stable/5.10: [f55261469be87c55df13db76dc945f6bcd825105]
stable/5.15: [b4af63da9d94986c529d74499fdfe44289acd551]
stable/5.4: [9dd334a8245011ace45e53298175c7b659edb3e7]
stable/6.1: [62f2e79cf9f4f47cc9dea9cebdf58d9f7b5695e0]
stable/6.6: [d7afdf360f4ac142832b098b4de974e867cc063c]
stable/6.7: [bfd0feb1b109cb63b87fdcd00122603787c75a1a]

CVE-2023-52488: erial: sc16is7xx: convert from _raw_ to _noinc_ regmap
functions for FIFO

Announce: https://lore.kernel.org/linux-cve-announce/20240229155245.1571576-29-lee@kernel.org/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit dfeae61 ("serial: sc16is7xx") in 3.16-rc1.
Fixed in 6.8-rc1.

Fixed status
mainline: [dbf4ab821804df071c8b566d9813083125e6d97b]
stable/6.1: [416b10d2817c94db86829fb92ad43ce7d002c573]
stable/6.6: [084c24e788d9cf29c55564de368bf5284f2bb5db]
stable/6.7: [aa7cb4787698add9367b19f7afc667662c9bdb23]

CVE-2023-52489: mm/sparsemem: fix race in accessing memory_section->usage

Announce: https://lore.kernel.org/linux-cve-announce/20240229155245.1571576-30-lee@kernel.org/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit f46edbd ("mm/sparsemem: add helpers track active
portions of a section at boot") in 5.3-rc1.
This commit is not backported to older stable kernels.
Fixed in 6/8-rc1.

Fixed status
mainline: [5ec8e8ea8b7783fab150cf86404fc38cb4db8800]
stable/5.10: [90ad17575d26874287271127d43ef3c2af876cea]
stable/5.15: [b448de2459b6d62a53892487ab18b7d823ff0529]
stable/6.1: [68ed9e33324021e9d6b798e9db00ca3093d2012a]
stable/6.6: [70064241f2229f7ba7b9599a98f68d9142e81a97]
stable/6.7: [3a01daace71b521563c38bbbf874e14c3e58adb7]

CVE-2023-52491: media: mtk-jpeg: Fix use after free bug due to error
path handling in mtk_jpeg_dec_device_run

Announce: https://lore.kernel.org/linux-cve-announce/20240229155245.1571576-32-lee@kernel.org/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit b2f0d27 ("[media] vcodec: mediatek: Add Mediatek
JPEG Decoder Driver") in 4.12-rc1.
This commit is not backported to older stable kernels.
Fixed in 6.8-rc1.

Fixed status
mainline: [206c857dd17d4d026de85866f1b5f0969f2a109e]
stable/5.10: [43872f44eee6c6781fea1348b38885d8e78face9]
stable/5.15: [1b1036c60a37a30caf6759a90fe5ecd06ec35590]
stable/6.1: [9fec4db7fff54d9b0306a332bab31eac47eeb5f6]
stable/6.6: [8254d54d00eb6cdb8367399c7f912eb8d354ecd7]
stable/6.7: [6e2f37022f0fc0893da4d85a0500c9d547fffd4c]

CVE-2023-52492: dmaengine: fix NULL pointer in channel unregistration function

Announce: https://lore.kernel.org/linux-cve-announce/20240229155245.1571576-33-lee@kernel.org/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit d2fb0a0 ("dmaengine: break out channel
registration") in 5.6-rc1.
This commit is not backported to older stable kernels.
Fixed in 6.8-rc1.

Fixed status
mainline: [f5c24d94512f1b288262beda4d3dcb9629222fc7]
stable/5.10: [9de69732dde4e443c1c7f89acbbed2c45a6a8e17]
stable/5.15: [047fce470412ab64cb7345f9ff5d06919078ad79]
stable/6.1: [2ab32986a0b9e329eb7f8f04dd57cc127f797c08]
stable/6.6: [7f0ccfad2031eddcc510caf4e57f2d4aa2d8a50b]
stable/6.7: [9263fd2a63487c6d04cbb7b74a48fb12e1e352d0]

CVE-2023-52493: bus: mhi: host: Drop chan lock before queuing buffers

Announce: https://lore.kernel.org/linux-cve-announce/20240229155245.1571576-34-lee@kernel.org/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 1d3173a ("bus: mhi: core: Add support for
processing events from client device") in 5.7-rc1.
This commit is not backported to older stable kernels.
Fixed in 6.8-rc1.

Fixed status
mainline: [01bd694ac2f682fb8017e16148b928482bc8fa4b]
stable/5.10: [20a6dea2d1c68d4e03c6bb50bc12e72e226b5c0e]
stable/5.15: [6e4c84316e2b70709f0d00c33ba3358d9fc8eece]
stable/6.1: [3c5ec66b4b3f6816f3a6161538672e389e537690]
stable/6.6: [eaefb9464031215d63c0a8a7e2bfaa00736aa17e]
stable/6.7: [b8eff20d87092e14cac976d057cb0aea2f1d0830]

CVE-2023-52494: bus: mhi: host: Add alignment check for event ring read pointer

Announce: https://lore.kernel.org/linux-cve-announce/20240229155245.1571576-35-lee@kernel.org/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit ec32332 ("bus: mhi: core: Sanity check values
from remote device before use") in 5.13-rc1.
This commit is backported to 5.19. Linux 5.4 and 4.x are not affected.
Fixed in 6.8-rc1.

Fixed status
mainline: [eff9704f5332a13b08fbdbe0f84059c9e7051d5f]
stable/5.15: [94991728c84f8df54fd9eec9b85855ef9057ea08]
stable/6.1: [2df39ac8f813860f79782807c3f7acff40b3c551]
stable/6.6: [a9ebfc405fe1be145f414eafadcbf09506082010]
stable/6.7: [ecf8320111822a1ae5d5fc512953eab46d543d0b]

CVE-2023-52497: erofs: fix lz4 inplace decompression

Announce: https://lore.kernel.org/linux-cve-announce/20240229155245.1571576-38-lee@kernel.org/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 0ffd71b ("staging: erofs: introduce LZ4
decompression inplace") in 5.3-rc1 and
598162d ("erofs: support decompress big pcluster for lz4 backend") in 5.13-rc1.
These commits are not backported to older stable kernels.
Fixed in 6.8-rc6.

Fixed status
mainline: [3c12466b6b7bf1e56f9b32c366a3d83d87afb4de]
stable/5.10: [a0180e940cf1aefa7d516e20b259ad34f7a8b379]
stable/5.15: [77cbc04a1a8610e303a0e0d74f2676667876a184]
stable/6.1: [33bf23c9940dbd3a22aad7f0cda4c84ed5701847]
stable/6.6: [f36d200a80a3ca025532ed60dd1ac21b620e14ae]
stable/6.7: [bffc4cc334c5bb31ded54bc3cfd651735a3cb79e]

CVE-2023-52498: PM: sleep: Fix possible deadlocks in core system-wide PM code

Announce: https://lore.kernel.org/linux-cve-announce/20240229155245.1571576-39-lee@kernel.org/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined. Fixed in 6.8-rc1.
This commit log contains 5.7+ tag so that it may not affect to prior to 5.7.

Fixed status
mainline: [7839d0078e0d5e6cc2fa0b0dfbee71de74f1e557]
stable/5.10: [f46eb832389f162ad13cb780d0b8cde93641990d]
stable/5.15: [a1d62c775b07213c73f81ae842424c74dd14b5f0]
stable/6.1: [e1c9d32c98309ae764893a481552d3f99d46cb34]
stable/6.6: [e681e29d1f59a04ef773296e4bebb17b1b79f8fe]
stable/6.7: [9bd3dce27b01c51295b60e1433e1dadfb16649f7]

CVE-2024-26607: drm/bridge: sii902x: Fix probing race issue

Announce: https://lore.kernel.org/linux-cve-announce/20240229133514.1480195-2-lee@kernel.org/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 21d8084 ("drm/bridge/sii902x: Fix EDID readback")
in 5.0-rc1.
This commit is not backported to older stable kernels.
Fixed in 6.8-rc2.

Fixed status
mainline: [08ac6f132dd77e40f786d8af51140c96c6d739c9]
stable/6.1: [e0f83c234ea7a3dec1f84e5d02caa1c51664a076]
stable/6.6: [56f96cf6eb11a1c2d594367c3becbfb06a855ec1]
stable/6.7: [2a4c6af7934a7b4c304542c38fee35e09cc1770c]

CVE-2024-26609: netfilter: nf_tables: reject QUEUE/DROP verdict parameters

Announce: https://lore.kernel.org/linux-cve-announce/20240229155245.1571576-41-lee@kernel.org/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit e0abdad ("netfilter: nf_tables: accept QUEUE/DROP
verdict parameters") in 3.15-rc1.
Fixed in 6.8-rc2.

Fixed status
mainline: [f342de4e2f33e0e39165d8639387aa6c19dff660]
stable/4.19: [8365e9d92b85fda975a5ece7a3a139cb964018c8]
stable/5.10: [55a60251fa50d4e68175e36666b536a602ce4f6c]
stable/5.15: [960cf4f812530f01f6acc6878ceaa5404c06af7b]
stable/5.4: [4e66422f1b56149761dc76030e6345d1cca6f869]
stable/6.1: [8e34430e33b8a80bc014f3efe29cac76bc30a4b4]
stable/6.6: [6653118b176a00915125521c6572ae8e507621db]
stable/6.7: [f05a497e7bc8851eeeb3a58da180ba469efebb05]

CVE-2024-26610: wifi: iwlwifi: fix a memory corruption

Announce: https://lore.kernel.org/linux-cve-announce/20240229155245.1571576-42-lee@kernel.org/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit cf29c5b ("iwlwifi: dbg_ini: implement time point
handling") in 5.5-rc1.
This commit is not backported to older stable kernels.
Fixed in 6.8-rc2.

mainline: [cf4a0d840ecc72fcf16198d5e9c505ab7d5a5e4d]
stable/5.10: [05dd9facfb9a1e056752c0901c6e86416037d15a]
stable/5.15: [99a23462fe1a6f709f0fda3ebbe8b6b193ac75bd]
stable/6.1: [aa2cc9363926991ba74411e3aa0a0ea82c1ffe32]
stable/6.6: [870171899d75d43e3d14360f3a4850e90a9c289b]
stable/6.7: [f32a81999d0b8e5ce60afb5f6a3dd7241c17dd67]

CVE-2024-26613: net/rds: Fix UBSAN: array-index-out-of-bounds in rds_cmsg_recv

Announce: https://lore.kernel.org/linux-cve-announce/20240229155245.1571576-45-lee@kernel.org/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 3289025 ("RDS: add receive message trace used by
application") in 4.11-rc1.
This commit is not backported to older stable kernels.
Fixed in 6.8-rc2.

Fixed status
mainline: [13e788deb7348cc88df34bed736c3b3b9927ea52]
stable/4.19: [344350bfa3b4b37d7c3d5a00536e6fbf0e953fbf]
stable/5.10: [5ae8d50044633306ff160fcf7faa24994175efe1]
stable/5.15: [00d1ee8e1d02194f7b7b433e904e04bbcd2cc0dc]
stable/5.4: [a37ae111db5e0f7e3d6b692056c30e3e0f6f79cd]
stable/6.1: [71024928b3f71ce4529426f8692943205c58d30b]
stable/6.6: [7a73190ea557e7f26914b0fe04c1f57a96cb771f]
stable/6.7: [0b787c2dea15e7a2828fa3a74a5447df4ed57711]

CVE-2024-26614: tcp: make sure init the accept_queue''s spinlocks once

Announce: https://lore.kernel.org/linux-cve-announce/20240229155245.1571576-46-lee@kernel.org/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit fff1f30 ("tcp: add a spinlock to protect struct
request_sock_queue") in 4.4-rc1 and
168a8f5 ("tcp: TCP Fast Open Server - main code path") in 3.7-rc1.
Fixed in 6.8-rc2.

Fixed status
mainline: [198bc90e0e734e5f98c3d2833e8390cac3df61b2]
stable/5.10: [bc99dcedd2f422d602516762b96c8ef1ae6b2882]
stable/5.15: [d86cc6ab33b085eaef27ea88b78fc8e2375c0ef3]
stable/6.1: [b1e0a68a0cd2a83259c444f638b417a8fffc6855]
stable/6.6: [168e7e599860654876c2a1102a82610285c02f02]
stable/6.7: [3982fe726a63fb3de6005e534e2ac8ca7e0aca2a]

CVE-2024-26615: net/smc: fix illegal rmb_desc access in SMC-D connection dump

Announce: https://lore.kernel.org/linux-cve-announce/20240229155245.1571576-47-lee@kernel.org/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 4b1b7d3 ("net/smc: add SMC-D diag support") in 4.19-rc1.
This commit is not backported to older stable kernels.
Fixed in 6.8-rc2.

Fixed status
mainline: [dbc153fd3c142909e564bb256da087e13fbf239c]
stable/4.19: [27aea64838914c6122db5b8bd4bed865c9736f22]
stable/5.10: [5fed92ca32eafbfae8b6bee8ca34cca71c6a8b6d]
stable/5.15: [68b888d51ac82f2b96bf5e077a31d76afcdef25a]
stable/5.4: [1fea9969b81c67d0cb1611d1b8b7d19049d937be]
stable/6.1: [6994dba06321e3c48fdad0ba796a063d9d82183a]
stable/6.6: [a164c2922675d7051805cdaf2b07daffe44f20d9]
stable/6.7: [8f3f9186e5bb96a9c9654c41653210e3ea7e48a6]

CVE-2024-26618: arm64/sme: Always exit sme_alloc() early with existing storage

Introduced by commit 5d0a8d2 ("arm64/ptrace: Ensure that SME is set up
for target when writing SSVE state") in 6.5-rc7.
This commit is backported to 6.1. Linux 5.x and 4.x are not affected.
Fixed in 6.8-rc1.

Fixed status
mainline: [dc7eb8755797ed41a0d1b5c0c39df3c8f401b3d9]
stable/6.6: [569156e4fa347237f8fa2a7e935d860109c55ac4]
stable/6.7: [814af6b4e6000e574e74d92197190edf07cc3680]

CVE-2021-47059: crypto: sun8i-ss - fix result memory leak on error path

Announce: https://lore.kernel.org/linux-cve-announce/2024022952-CVE-2021-47059-4bb8@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit d9b4541 ("crypto: sun8i-ss - support hash
algorithms") in 5.10-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [1dbc6a1e25be8575d6c4114d1d2b841a796507f7]
stable/5.10: [1f12aaf07f61122cf5074d29714ee26f8d44b0e7]

CVE-2021-47070: uio_hv_generic: Fix another memory leak in error handling paths

Announce: https://lore.kernel.org/linux-cve-announce/2024030141-CVE-2021-47070-0525@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit cdfa835 ("uio_hv_generic: defer opening vmbus
until first use" in 4.20-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc3.

Fixed status
mainline: [0b0226be3a52dadd965644bc52a807961c2c26df]

CVE-2021-47074: nvme-loop: fix memory leak in nvme_loop_create_ctrl()

Announce: https://lore.kernel.org/linux-cve-announce/2024030142-CVE-2021-47074-46a7@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 3a85a5d ("nvme-loop: add a NVMe loopback host
driver") in 4.8-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc3.

Fixed status
mainline: [03504e3b54cc8118cc26c064e60a0b00c2308708]
stable/5.10: [9c980795ccd77e8abec33dd6fe28dfe1c4083e65]

CVE-2021-47076: RDMA/rxe: Return CQE error if invalid lkey was supplied

Announce: https://lore.kernel.org/linux-cve-announce/2024030142-CVE-2021-47076-a6b6@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit in 8700e3e ("Soft RoCE driver") in 4.8-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc3.

Fixed status
mainline: [dc07628bd2bbc1da768e265192c28ebd301f509d]

CVE-2021-47077: scsi: qedf: Add pointer checks in qedf_update_link_speed()

Announce: https://lore.kernel.org/linux-cve-announce/2024030142-CVE-2021-47077-994b@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 61d8658 ("scsi: qedf: Add QLogic FastLinQ offload
FCoE driver framework.") in 4.11-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc3.

Fixed status
mainline: [73578af92a0fae6609b955fcc9113e50e413c80f]
stable/5.10: [a6362a737572f66051deb7637f3f77ddf7a4402f]

CVE-2021-47073: platform/x86: dell-smbios-wmi: Fix oops on rmmod dell_smbios

Announce: https://lore.kernel.org/linux-cve-announce/2024030142-CVE-2021-47073-704a@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 1a258e6 ("platform/x86: dell-smbios-wmi: Add new
WMI dispatcher driver") in 4.15-rc1.
Linux 4.4 is not affected.
Fixed in 5.13-rc3.

Fixed status
mainline: [3a53587423d25c87af4b4126a806a0575104b45e]
stable/4.19: [75cfc833da4a2111106d4c134e93e0c7f41e35e7]
stable/5.10: [0cf036a0d325200e6c27b90908e51195bbc557b1]
stable/5.4: [6fa78a6b9a3beb676a010dc489c1257f7e432525]

CVE-2021-47079: platform/x86: ideapad-laptop: fix a NULL pointer dereference

Announce: https://lore.kernel.org/linux-cve-announce/2024030142-CVE-2021-47079-3934@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit ff36b0d ("platform/x86: ideapad-laptop: rework
and create new ACPI helpers") in 5.12-rc1-dontuse.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc3.

Fixed status
mainline: [ff67dbd554b2aaa22be933eced32610ff90209dd]

CVE-2021-47071: uio_hv_generic: Fix a memory leak in error handling paths

Announce: https://lore.kernel.org/linux-cve-announce/2024030141-CVE-2021-47071-cd46@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit cdfa835 ("uio_hv_generic: defer opening vmbus
until first use") in 4.20-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc3.

Fixed status
mainline: [3ee098f96b8b6c1a98f7f97915f8873164e6af9d]
stable/5.10: [d84b5e912212b05f6b5bde9f682046accfbe0354]
stable/5.4: [cdd91637d4ef33e2be19a8e16e72e7d00c996d76]

CVE-2021-47080: RDMA/core: Prevent divide-by-zero error triggered by the user

Announce: https://lore.kernel.org/linux-cve-announce/2024030142-CVE-2021-47080-eb20@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 9f85cbe ("RDMA/uverbs: Expose the new GID query
API to user space") in 5.10-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc3.

Fixed status
mainline: [54d87913f147a983589923c7f651f97de9af5be1]
stable/5.10: [66ab7fcdac34b890017f04f391507ef5b2b89a13]

CVE-2021-47075: nvmet: fix memory leak in nvmet_alloc_ctrl()

Announce: https://lore.kernel.org/linux-cve-announce/2024030142-CVE-2021-47075-8d12@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 94a39d6 ("nvmet: make ctrl-id configurable") in 5.7-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc3.

Fixed status
mainline: [fec356a61aa3d3a66416b4321f1279e09e0f256f]
stable/5.10: [4720f29acb3fe67aa8aa71e6b675b079d193aaeb]

CVE-2021-47078: RDMA/rxe: Clear all QP fields if creation failed

Announce: https://lore.kernel.org/linux-cve-announce/2024030142-CVE-2021-47078-71f9@gregkh/T/#u

Introduced by commit 8700e3e ("Soft RoCE driver") in 4.8-rc1.
Linux 4.4 is not affected.
Fixed in 5.13-rc3.

Fixed status
mainline: [67f29896fdc83298eed5a6576ff8f9873f709228]
stable/4.19: [f3783c415bf6d2ead3d7aa2c38802bbe10723646]
stable/5.10: [2ee4d79c364914989c80de382c0b1a7259a7e4b3]
stable/5.4: [a62225d951d77eb20208fed8fc199e0c9b1df08b]

CVE-2021-47081: habanalabs/gaudi: Fix a potential use after free in
gaudi_memset_device_memory

Announce: https://lore.kernel.org/linux-cve-announce/2024030143-CVE-2021-47081-e590@gregkh/T/#u

Introduced by commit 423815b ("habanalabs/gaudi: remove PCI access to
SM block") in 5.12-rc1-dontuse.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc3.

Fixed status
mainline: [115726c5d312b462c9d9931ea42becdfa838a076]

CVE-2021-47069: ipc/mqueue, msg, sem: avoid relying on a stack
reference past its expiry

Announce: https://lore.kernel.org/linux-cve-announce/2024030141-CVE-2021-47069-5797@gregkh/T/#u

Introduced by commit c5b2cbd ("ipc/mqueue.c: update/document memory
barriers") in 5.6-rc1 and
8116b54 ("ipc/sem.c: document and update memory barriers") in 5.6-rc1 and
0d97a82 ("ipc/msg.c: update and document memory barriers") in 5.6-rc1.
These commits are not backported to older stable kernels.
Fixed in 5.13-rc3.

Fixed status
mainline: [a11ddb37bf367e6b5239b95ca759e5389bb46048]
stable/5.10: [4528c0c323085e645b8765913b4a7fd42cf49b65]

CVE-2021-47072: btrfs: fix removed dentries still existing after log is synced

Announce: https://lore.kernel.org/linux-cve-announce/2024030141-CVE-2021-47072-52d4@gregkh/T/#u

Introduced by commit 64d6b28 ("btrfs: remove unnecessary
check_parent_dirs_for_sync()") in 5.12-rc1-dontuse.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc3.

Fixed status
mainline: [54a40fc3a1da21b52dbf19f72fdc27a2ec740760]

CVE-2023-52477: usb: hub: Guard against accesses to uninitialized BOS
descriptors

Announce: usb: hub: Guard against accesses to uninitialized BOS descriptors

Introduced commit is not determined. It looks as if Linux 4.4 may be
affected too.
Fixed in 6.6-rc6.

Fixed status
mainline: [f74a7afc224acd5e922c7a2e52244d891bbe44ee]
stable/4.19: [8e7346bfea56453e31b7421c1c17ca2fb9ed613d]
stable/5.10: [241f230324337ed5eae3846a554fb6d15169872c]
stable/5.15: [528f0ba9f7a4bc1b61c9b6eb591ff97ca37cac6b]
stable/5.4: [6ad3e9fd3632106696692232bf7ff88b9f7e1bc3]
stable/6.1: [fb9895ab9533534335fa83d70344b397ac862c81]

CVE-2023-52487: net/mlx5e: Fix peer flow lists handling

Announce: https://lore.kernel.org/linux-cve-announce/20240229155245.1571576-28-lee@kernel.org/T/#u

Introduced by commit 9be6c21 ("net/mlx5e: Handle offloads flows per
peer") in 6.5-rc1.
This commit is not backported to older stable kernels.
Fixed in 6.8-rc2.

Fixed status
mainline: [d76fdd31f953ac5046555171620f2562715e9b71]
stable/6.6: [74cec142f89bf85c6c99c5db957da9f663f9f16f]
stable/6.7: [e24d6f5a7f2d95a98a46257a5a5a5381d572894f]

CVE-2023-52495: soc: qcom: pmic_glink_altmode: fix port sanity check

Announce: https://lore.kernel.org/linux-cve-announce/20240229155245.1571576-36-lee@kernel.org/T/#u

Introduced by commit 080b4e2 ("soc: qcom: pmic_glink: Introduce
altmode support") in 6.3-rc1.
This commit is not backported to older stable kernels.
Fixed in 6.8-rc1.

Fixed status
mainline: [c4fb7d2eac9ff9bfc35a2e4d40c7169a332416e0]
stable/6.6: [532a5557da6892a6b2d5793052e1bce1f4c9e177]
stable/6.7: [d26edf4ee3672cc9828f2a3ffae34086a712574d]

CVE-2023-52496: mtd: maps: vmu-flash: Fix the (mtd core) switch to ref counters

Announce: https://lore.kernel.org/linux-cve-announce/20240229155245.1571576-37-lee@kernel.org/T/#u

Introduced by commit 19bfa9e ("mtd: use refcount to prevent
corruption") in 6.6-rc1.
This commit is not backported to older stable kernels.
Fixed in 6.8-rc1.

Fixed status
mainline: [a7d84a2e7663bbe12394cc771107e04668ea313a]
stable/6.6: [38c12f10990ad6e63ddef2f20c1b066e5e4d34fd]
stable/6.7: [1168d6b79d2fafb41299fbc1b528e20644c562a5]

CVE-2023-52490: mm: migrate: fix getting incorrect page mapping during
page migration

Announce: https://lore.kernel.org/linux-cve-announce/20240229155245.1571576-31-lee@kernel.org/T/#u

Introduced by commit 64c8902 ("migrate_pages: split unmap_and_move()
to _unmap() and _move()") in 6.3-rc1.
This commit is not backported to older stable kernels.
Fixed in 6.8-rc1.

Fixed status
mainline: [d1adb25df7111de83b64655a80b5a135adbded61]
stable/6.6: [9128bfbc5c80d8f4874dd0a0424d1f5fb010df1b]
stable/6.7: [3889a418b6eb9a1113fb989aaadecf2f64964767]

CVE-2023-52478: HID: logitech-hidpp: Fix kernel crash on receiver USB disconnect

Announce: https://lore.kernel.org/linux-cve-announce/2024022921-CVE-2023-52478-c0a1@gregkh/T/#u

Introduced commit is not determined. Fixed in 6.6-rc6.

Fixed status
cip/4.4: [60b2e00632dafe730b3e7f258b286b04b49d59e4]
cip/4.4-rt: [60b2e00632dafe730b3e7f258b286b04b49d59e4]
cip/4.4-st: [60b2e00632dafe730b3e7f258b286b04b49d59e4]
mainline: [dac501397b9d81e4782232c39f94f4307b137452]
stable/4.19: [44481b244fcaa2b895a53081d6204c574720c38c]
stable/5.10: [093af62c023537f097d2ebdfaa0bc7c1a6e874e1]
stable/5.15: [28ddc1e0b898291323b62d770b1b931de131a528]
stable/5.4: [cd0e2bf7fb22fe9b989c59c42dca06367fd10e6b]
stable/6.1: [fd72ac9556a473fc7daf54efb6ca8a97180d621d]

CVE-2023-52475: Input: powermate - fix use-after-free in
powermate_config_complete

Announce: https://lore.kernel.org/linux-cve-announce/2024022918-CVE-2023-52475-442e@gregkh/T/#u

Introduced commit is not determined. Fixed in 6.6-rc6.

Fixed status
cip/4.4: [a2557fa768734fc895d8201475a7dedd775089bb]
cip/4.4-rt: [a2557fa768734fc895d8201475a7dedd775089bb]
cip/4.4-st: [a2557fa768734fc895d8201475a7dedd775089bb]
mainline: [5c15c60e7be615f05a45cd905093a54b11f461bc]
stable/4.19: [67cace72606baf1758fd60feb358f4c6be92e1cc]
stable/5.10: [cd2fbfd8b922b7fdd50732e47d797754ab59cb06]
stable/5.15: [6a4a396386404e62fb59bc3bde48871a64a82b4f]
stable/5.4: [5aa514100aaf59868d745196258269a16737c7bd]
stable/6.1: [2efe67c581a2a6122b328d4bb6f21b3f36f40d46]

CVE-2023-52483: mctp: perform route lookups under a RCU read-side lock

Announce: https://lore.kernel.org/linux-cve-announce/2024022923-CVE-2023-52483-5b9d@gregkh/T/#u

Introduced by commit 889b7da ("mctp: Add initial routing framework")
in 5.15-rc1.
This commit is not backported to older stable kernels.
Fixed in 6.6-rc6.

Fixed status
mainline: [5093bbfc10ab6636b32728e35813cbd79feb063c]
stable/5.15: [6c52b12159049046483fdb0c411a0a1869c41a67]
stable/6.1: [1db0724a01b558feb1ecae551782add1951a114a]

CVE-2024-26612: netfs, fscache: Prevent Oops in fscache_put_cache()

Announce: https://lore.kernel.org/linux-cve-announce/20240229155245.1571576-44-lee@kernel.org/T/#u

Introduced by commit 9549332 ("fscache: Implement cache registration")
in 5.17-rc1.
This commit is not backported to older stable kernels.
Fixed in 6.8-rc2.

Fixed status
mainline: [3be0b3ed1d76c6703b9ee482b55f7e01c369cc68]
stable/6.1: [82a9bc343ba019665d3ddc1d9a180bf0e0390cf3]
stable/6.6: [1c45256e599061021e2c848952e50f406457e448]
stable/6.7: [4200ad3e46ce50f410fdda302745489441bc70f0]

CVE-2024-26617: fs/proc/task_mmu: move mmu notification mechanism inside mm lock

Announce: https://lore.kernel.org/linux-cve-announce/20240229155245.1571576-49-lee@kernel.org/T/#u

Introduced by commit 52526ca ("fs/proc/task_mmu: implement IOCTL to
get and optionally clear info about PTEs") in 6.7-rc1.
This commit is not backported to older stable kernels.
Fixed in 6.8-rc1.

Fixed status
mainline: [4cccb6221cae6d020270606b9e52b1678fc8b71a]
stable/6.7: [05509adf297924f51e1493aa86f9fcde1433ed80]

CVE-2024-26616: btrfs: scrub: avoid use-after-free when chunk length
is not 64K aligned

Announce: https://lore.kernel.org/linux-cve-announce/20240229155245.1571576-48-lee@kernel.org/T/#u

Introduced by commit e02ee89 ("btrfs: scrub: switch
scrub_simple_mirror() to scrub_stripe infrastructure") in 6.4-rc1.
This commit is not backported to older stable kernels.
Fixed in 6.8-rc2.

Fixed status
mainline: [f546c4282673497a06ecb6190b50ae7f6c85b02f]
stable/6.6: [642b9c520ef2f104277ad1f902f8526edbe087fb]
stable/6.7: [34de0f04684ec00c093a0455648be055f0e8e24f]

CVE-2024-26611: xsk: fix usage of multi-buffer BPF helpers for ZC XDP

Announce: https://lore.kernel.org/linux-cve-announce/20240229155245.1571576-43-lee@kernel.org/T/#u

Introduced by commit 24ea501 ("xsk: support mbuf on ZC RX") in 6.6-rc1.
This commit is not backported to older stable kernels.
Fixed in 6.8-rc2.

Fixed status
mainline: [c5114710c8ce86b8317e9b448f4fd15c711c2a82]
stable/6.6: [82ee4781b8200e44669a354140d5c6bd966b8768]
stable/6.7: [5cd781f7216f980207af09c5e0e1bb1eda284540]

CVE-2024-26608: ksmbd: fix global oob in ksmbd_nl_policy

Announce: https://lore.kernel.org/linux-cve-announce/20240229155245.1571576-40-lee@kernel.org/T/#u

Introduced by commit 0626e66 ("cifsd: add server handler for central
processing and tranport layers") in 5.15-rc1.
ksmbd is introduced in 5.15 so 5.10, 5.4, and 4.x kernels are not affected.
Fixed in 6.8-rc2.

Fixed status
mainline: [ebeae8adf89d9a82359f6659b1663d09beec2faa]
stable/5.15: [aaa1f1a2ee80888c12ae2783f3a0be10e14067c5]
stable/6.1: [2c939c74ef0b74e99b92e32edc2a59f9b9ca3d5a]
stable/6.6: [9863a53100f47652755545c2bd43e14a1855104d]
stable/6.7: [6993328a4cd62a24df254b587c0796a4a1eecc95]

CVE-2024-26620: s390/vfio-ap: always filter entire AP matrix

Announce: https://lore.kernel.org/linux-cve-announce/20240229155245.1571576-52-lee@kernel.org/T/#u

Introduced by commit 48cae94 ("s390/vfio-ap: refresh guest's APCB by
filtering AP resources assigned to mdev") in 6.0-rc1.
This commit is not backported to older stable kernels.
Fixed in 6.8-rc1.

Fixed status
mainline: [850fb7fa8c684a4c6bf0e4b6978f4ddcc5d43d11]
stable/6.1: [d6b8d034b576f406af920a7bee81606c027b24c6]
stable/6.6: [c69d821197611678533fb3eb784fc823b921349a]
stable/6.7: [cdd134d56138302976685e6c7bc4755450b3880e]

CVE-2024-26619: riscv: Fix module loading free order

Announce: https://lore.kernel.org/linux-cve-announce/20240229155245.1571576-51-lee@kernel.org/T/#u

Introduced by commit d8792a5 ("riscv: Safely remove entries from
relocation list") in 6.7-rc5.
This commit is not backported to older stable kernels.
Fixed in 6.8-rc1.

Fixed status
mainline: [78996eee79ebdfe8b6f0e54cb6dcc792d5129291]
stable/6.7: [2fa79badf4bfeffda6b5032cf62b828486ec9a99]

CVE-2022-48627: vt: fix memory overlapping when deleting chars in the buffer

Announce: https://lore.kernel.org/linux-cve-announce/2024030252-CVE-2022-48627-c7bf@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 81732c3 ("tty vt: Fix line garbage in virtual
console on command line edition") in v3.7-rc1.
Fixed in v5.19-rc7.

Fixed status
mainline: [39cdb68c64d84e71a4a717000b6e5de208ee60cc]
stable/5.10: [bfee93c9a6c395f9aa62268f1cedf64999844926]
stable/5.15: [57964a5710252bc82fe22d9fa98c180c58c20244]

CVE-2022-48628: ceph: drop messages from MDS when unmounting

Announce: https://lore.kernel.org/linux-cve-announce/2024030245-CVE-2022-48628-181a@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.6-rc1.

Fixed status
mainline: [e3dfcab2080dc1f9a4b09cc1327361bc2845bfcd]
stable/6.1: [89744b64914426cbabceb3d8a149176b5dafdfb5]

CVE-2023-52499: powerpc/47x: Fix 47x syscall return crash

Announce: https://lore.kernel.org/linux-cve-announce/2024030247-CVE-2023-52499-1b6f@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 6f76a01 ("powerpc/syscall: implement system call
entry/exit logic in C for PPC32") in v5.12-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.6-rc6.

Fixed status
mainline: [f0eee815babed70a749d2496a7678be5b45b4c14]
stable/5.15: [29017ab1a539101d9c7bec63cc13a019f97b2820]
stable/6.1: [8ac2689502f986a46f4221e239d4ff2897f1ccb3]

CVE-2023-52500: scsi: pm80xx: Avoid leaking tags when processing
OPC_INB_SET_CONTROLLER_CONFIG command

Announce: https://lore.kernel.org/linux-cve-announce/2024030248-CVE-2023-52500-3d53@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.6-rc2.

Fixed status
mainline: [c13e7331745852d0dd7c35eabbe181cbd5b01172]
stable/5.10: [2afd8fcee0c4d65a482e30c3ad2a92c25e5e92d4]
stable/5.15: [d540a4370aba378fbedf349ba0bb68e96e24243d]
stable/6.1: [2259e1901b2d8c0e8538fc99e77de443b939e749]

CVE-2023-52501: ring-buffer: Do not attempt to read past "commit"

Announce: https://lore.kernel.org/linux-cve-announce/2024030248-CVE-2023-52501-75ba@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.6-rc2.
It seems as if 4.19 and 4.4 are affected.

Fixed status
mainline: [95a404bd60af6c4d9d8db01ad14fe8957ece31ca]
stable/5.10: [cee5151c5410e868826b8afecfb356f3799ebea3]
stable/5.15: [344f2f3e61a90f0150c754796ec9a17fcaeec03d]
stable/6.1: [b08a4938229dbb530a35c41b83002a1457c6ff49]

CVE-2023-52502: net: nfc: fix races in nfc_llcp_sock_get() and
nfc_llcp_sock_get_sn()

Announce: https://lore.kernel.org/linux-cve-announce/2024030248-CVE-2023-52502-6863@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 8f50020 ("NFC: LLCP late binding") in v3.6-rc1.
Fixed in v6.6-rc6.

Fixed status
mainline: [31c07dffafce914c1d1543c135382a11ff058d93]
stable/4.19: [e863f5720a5680e50c4cecf12424d7cc31b3eb0a]
stable/5.10: [6ac22ecdaad2ecc662048f8c6b0ceb1ca0699ef9]
stable/5.15: [d888d3f70b0de32b4f51534175f039ddab15eef8]
stable/5.4: [7adcf014bda16cdbf804af5c164d94d5d025db2d]
stable/6.1: [e4f2611f07c87b3ddb57c4b9e8efcd1e330fc3dc]

CVE-2023-52503: tee: amdtee: fix use-after-free vulnerability in
amdtee_close_session

Announce: https://lore.kernel.org/linux-cve-announce/2024030248-CVE-2023-52503-cb3a@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 757cc3e ("tee: add AMD-TEE driver") in v5.6-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.6-rc6.

Fixed status
mainline: [f4384b3e54ea813868bb81a861bf5b2406e15d8f]
stable/5.10: [da7ce52a2f6c468946195b116615297d3d113a27]
stable/5.15: [1680c82929bc14d706065f123dab77f2f1293116]
stable/6.1: [60c3e7a00db954947c265b55099c21b216f2a05c]

CVE-2023-52504: x86/alternatives: Disable KASAN in apply_alternatives()

Announce: https://lore.kernel.org/linux-cve-announce/2024030249-CVE-2023-52504-ebc5@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 6657fca ("x86/mm: Allow to boot without LA57 if
CONFIG_X86_5LEVEL=y") in v4.17-rc1.
Linux 4.4 is not affected.
Fixed in v6.6-rc6.

Fixed status
mainline: [d35652a5fc9944784f6f50a5c979518ff8dacf61]
stable/4.19: [3719d3c36aa853d5a2401af9f8d6b116c91ad5ae]
stable/5.10: [6788b10620ca6e98575d1e06e72a8974aad7657e]
stable/5.15: [ecba5afe86f30605eb9dfb7f265a8de0218d4cfc]
stable/5.4: [3770c38cd6a60494da29ac2da73ff8156440a2d1]
stable/6.1: [5b784489c8158518bf7a466bb3cc045b0fb66b4b]

CVE-2023-52505: phy: lynx-28g: serialize concurrent phy_set_mode_ext()
calls to shared registers

Announce: https://lore.kernel.org/linux-cve-announce/2024030249-CVE-2023-52505-8ac5@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 8f73b37 ("phy: add support for the Layerscape
SerDes 28G") in v5.18-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.6-rc6.

Fixed status
mainline: [139ad1143151a07be93bf741d4ea7c89e59f89ce]
stable/6.1: [6f901f8448c6b25ed843796b114471d2a3fc5dfb]

CVE-2023-52506: LoongArch: Set all reserved memblocks on Node#0 at
initialization

Announce: https://lore.kernel.org/linux-cve-announce/2024030249-CVE-2023-52506-2b5a@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.6-rc3.
The LoonArch architecture is introduced in 5.19.

Fixed status
mainline: [b795fb9f5861ee256070d59e33130980a01fadd7]
stable/6.1: [f105e893a8edd48bdf4bef9fef845a9ff402f737]

CVE-2023-52507: nfc: nci: assert requested protocol is valid

Announce: https://lore.kernel.org/linux-cve-announce/2024030249-CVE-2023-52507-030c@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 6a2968a ("NFC: basic NCI protocol
implementation") in v3.2-rc1.
Fixed in v6.6-rc6.

Fixed status
cip/4.4: [b33ea19edf8559941bd5b924fd2433cbc9eadd58]
cip/4.4-rt: [b33ea19edf8559941bd5b924fd2433cbc9eadd58]
cip/4.4-st: [b33ea19edf8559941bd5b924fd2433cbc9eadd58]
mainline: [354a6e707e29cb0c007176ee5b8db8be7bd2dee0]
stable/4.19: [a686f84101680b8442181a8846fbd3c934653729]
stable/5.10: [a424807d860ba816aaafc3064b46b456361c0802]
stable/5.15: [25dd54b95abfdca423b65a4ee620a774777d8213]
stable/5.4: [95733ea130e35ef9ec5949a5908dde3feaba92cb]
stable/6.1: [853dda54ba59ea70d5580a298b7ede4707826848]

CVE-2023-52508: nvme-fc: Prevent null pointer dereference in
nvme_fc_io_getuuid()

Announce: https://lore.kernel.org/linux-cve-announce/2024030250-CVE-2023-52508-359c@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.6-rc2.
Vulnerable function is introduced by commit 827fc630e ("scsi: nvme-fc:
Add new routine nvme_fc_io_getuuid()") in 5.19-rc1.

Fixed status
mainline: [8ae5b3a685dc59a8cf7ccfe0e850999ba9727a3c]
stable/6.1: [be90c9e29dd59b7d19a73297a1590ff3ec1d22ea]

CVE-2023-52509: ravb: Fix use-after-free issue in ravb_tx_timeout_work()

Announce: https://lore.kernel.org/linux-cve-announce/2024030250-CVE-2023-52509-997c@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit c156633 ("Renesas Ethernet AVB driver proper") in v4.2-rc1.
Fixed in v6.6-rc6.

Fixed status
mainline: [3971442870713de527684398416970cf025b4f89]
stable/5.10: [db9aafa19547833240f58c2998aed7baf414dc82]
stable/5.15: [616761cf9df9af838c0a1a1232a69322a9eb67e6]
stable/5.4: [65d34cfd4e347054eb4193bc95d9da7eaa72dee5]
stable/6.1: [6f6fa8061f756aedb93af12a8a5d3cf659127965]

CVE-2023-52510: ieee802154: ca8210: Fix a potential UAF in ca8210_probe

Announce: https://lore.kernel.org/linux-cve-announce/2024030250-CVE-2023-52510-6f8a@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit ded845a ("ieee802154: Add CA8210 IEEE 802.15.4
device driver") in v4.12-rc1.
Linux 4.4 is not affected.
Fixed in v6.6-rc6.

Fixed status
mainline: [f990874b1c98fe8e57ee9385669f501822979258]
stable/4.19: [cdb46be93c1f7bbf2c4649e9fc5fb147cfb5245d]
stable/5.10: [55e06850c7894f00d41b767c5f5665459f83f58f]
stable/5.15: [84c6aa0ae5c4dc121f9996bb8fed46c80909d80e]
stable/5.4: [85c2857ef90041f567ce98722c1c342c4d31f4bc]
stable/6.1: [217efe32a45249eb07dcd7197e8403de98345e66]

CVE-2023-52511: spi: sun6i: reduce DMA RX transfer width to single byte

Announce: https://lore.kernel.org/linux-cve-announce/2024030250-CVE-2023-52511-1dbc@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.6-rc1.
Vulnerable function sun6i_spi_prepare_dma() is introcued by commit
345980a  ("spi: spi-sun6i: implement DMA-based transfer mode") in
5.11-rc1.

Fixed status
mainline: [171f8a49f212e87a8b04087568e1b3d132e36a18]
stable/5.15: [ff05ed4ae214011464a0156f05cac1b0b46b5fbc]
stable/6.1: [e15bb292b24630ee832bfc7fd616bd72c7682bbb]

CVE-2023-52512: pinctrl: nuvoton: wpcm450: fix out of bounds write

Announce: https://lore.kernel.org/linux-cve-announce/2024030251-CVE-2023-52512-92f7@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit a1d1e0e ("pinctrl: nuvoton: Add driver for
WPCM450") in v5.18-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.6-rc6.

Fixed status
mainline: [87d315a34133edcb29c4cadbf196ec6c30dfd47b]
stable/6.1: [6c18c386fd13dbb3ff31a1086dabb526780d9bda]

CVE-2023-52513: RDMA/siw: Fix connection failure handling

Announce: https://lore.kernel.org/linux-cve-announce/2024030251-CVE-2023-52513-5224@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 6c52fdc ("rdma/siw: connection management") in v5.3-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.6-rc5.

Fixed status
mainline: [53a3f777049771496f791504e7dc8ef017cba590]
stable/5.10: [0d520cdb0cd095eac5d00078dfd318408c9b5eed]
stable/5.15: [81b7bf367eea795d259d0261710c6a89f548844d]
stable/5.4: [6e26812e289b374c17677d238164a5a8f5770594]
stable/6.1: [5cf38e638e5d01b68f9133968a85e8b3fd1ecf2f]

CVE-2023-52514: x86/reboot: VMCLEAR active VMCSes before emergency reboot

Announce: https://lore.kernel.org/linux-cve-announce/2024030251-CVE-2023-52514-c93d@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.6-rc1.

Fixed status
mainline: [b23c83ad2c638420ec0608a9de354507c41bec29]
stable/6.1: [1375d9600c38c231163de584656b07aef9a27b0d]

CVE-2023-52515: RDMA/srp: Do not call scsi_done() from srp_abort()

Announce: https://lore.kernel.org/linux-cve-announce/2024030251-CVE-2023-52515-5af7@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit d853667 ("IB/srp: Avoid having aborted requests
hang") in v3.7-rc1.
Fixed in v6.6-rc5.

Fixed status
mainline: [e193b7955dfad68035b983a0011f4ef3590c85eb]
stable/5.10: [26788a5b48d9d5cd3283d777d238631c8cd7495a]
stable/5.15: [b9bdffb3f9aaeff8379c83f5449c6b42cb71c2b5]
stable/6.1: [2b298f9181582270d5e95774e5a6c7a7fb5b1206]

CVE-2023-52516: dma-debug: don't call __dma_entry_alloc_check_leak()
under free_entries_lock

Announce: https://lore.kernel.org/linux-cve-announce/2024030252-CVE-2023-52516-9b4a@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.6-rc1.

Fixed status
mainline: [fb5a4315591dae307a65fc246ca80b5159d296e1]
stable/5.10: [c79300599923daaa30f417c75555d5566b3d31ae]
stable/5.15: [ac0d068099349cbca3d93f2e3b15bb329364b08c]
stable/6.1: [be8f49029eca3efbad0d74dbff3cb9129994ffab]

CVE-2023-52517: spi: sun6i: fix race between DMA RX transfer
completion and RX FIFO drain

Announce: https://lore.kernel.org/linux-cve-announce/2024030252-CVE-2023-52517-30dc@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.6-rc1.

Fixed status
mainline: [1f11f4202caf5710204d334fe63392052783876d]
stable/5.15: [bd1ec7f9983b5cd3c77e0f7cda3fa8aed041af2f]
stable/6.1: [36b29974a7ad2ff604c24ad348f940506c7b1209]

CVE-2023-52518: Bluetooth: hci_codec: Fix leaking content of local_codecs

Announce: https://lore.kernel.org/linux-cve-announce/2024030251-CVE-2023-52518-bcfa@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 8961987 ("Bluetooth: Enumerate local supported
codec and cache details") in v5.16-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.6-rc5.

Fixed status
mainline: [b938790e70540bf4f2e653dcd74b232494d06c8f]
stable/6.1: [626535077ba9dc110787540d1fe24881094c15a1]

CVE-2023-52519: HID: intel-ish-hid: ipc: Disable and reenable ACPI GPE bit

Announce: https://lore.kernel.org/linux-cve-announce/2024030252-CVE-2023-52519-d53f@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 2e23a70 ("HID: intel-ish-hid: ipc: finish power
flow for EHL OOB") in v5.12-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.6-rc5.

Fixed status
mainline: [8f02139ad9a7e6e5c05712f8c1501eebed8eacfd]
stable/5.15: [8781fe259dd5a178fdd1069401bbd1437f9491c5]
stable/6.1: [cdcc04e844a2d22d9d25cef1e8e504a174ea9f8f]

CVE-2023-52520: platform/x86: think-lmi: Fix reference leak

Announce: https://lore.kernel.org/linux-cve-announce/2024030252-CVE-2023-52520-0a4e@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 1bcad8e ("platform/x86: think-lmi: Fix issues
with duplicate attributes") in v5.14-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.6-rc5.

Fixed status
mainline: [528ab3e605cabf2f9c9bd5944d3bfe15f6e94f81]
stable/5.15: [124cf0ea4b82e1444ec8c7420af4e7db5558c293]
stable/6.1: [af21c9119a37cecb7ff27ce0c2f3cf721e9d0ec4]

CVE-2023-52521: bpf: Annotate bpf_long_memcpy with data_race

Announce: https://lore.kernel.org/linux-cve-announce/2024030253-CVE-2023-52521-d847@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

This CVE is rejected
Introduced commit is not determined.Fixed in v6.6-rc1.
The bpf_long_memcpy function is introduced in15a07b33 ("bpf: add
lookup/update support for per-cpu hash and array maps") in 4.6-rc1.

Fixed status
mainline: [6a86b5b5cd76d2734304a0173f5f01aa8aa2025e]
stable/6.1: [5685f8a6fae1fbe480493b980a1fdbe67c86a094]

CVE-2023-52522: net: fix possible store tearing in neigh_periodic_work()

Announce: https://lore.kernel.org/linux-cve-announce/2024030253-CVE-2023-52522-6abd@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 767e97e ("neigh: RCU conversion of struct
neighbour") in v2.6.37-rc1.
Fixed in v6.6-rc5.

Fixed status
mainline: [25563b581ba3a1f263a00e8c9a97f5e7363be6fd]
stable/5.10: [2ea52a2fb8e87067e26bbab4efb8872639240eb0]
stable/5.15: [147d89ee41434b97043c2dcb17a97dc151859baa]
stable/5.4: [95eabb075a5902f4c0834ab1fb12dc35730c05af]
stable/6.1: [f82aac8162871e87027692b36af335a2375d4580]

CVE-2023-52523: bpf, sockmap: Reject sk_msg egress redirects to non-TCP sockets

Announce: https://lore.kernel.org/linux-cve-announce/2024030253-CVE-2023-52523-5ae2@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 122e6c7 ("sock_map: Update sock type checks for
UDP") in v5.13-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.6-rc5.

Fixed status
mainline: [b80e31baa43614e086a9d29dc1151932b1bd7fc5]
stable/5.15: [bc8b89b6963803a123f64aa9494155a037b3d728]
stable/6.1: [b8f97e47b6fb84fcf2f5a22e725eefb6cf5070c2]

CVE-2023-52524: net: nfc: llcp: Add lock when modifying device list

Announce: https://lore.kernel.org/linux-cve-announce/2024030253-CVE-2023-52524-a5e0@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 6709d4b ("net: nfc: Fix use-after-free caused by
nfc_llcp_find_local") in v6.5-rc1.
This commit is backported to 5.4, 5.10, 5.15, and 6.1. Linux 4.4 is
not affected.
Fixed in v6.6-rc5.

Fixed status
mainline: [dfc7f7a988dad34c3bf4c053124fb26aa6c5f916]
stable/5.10: [dba849cc98113b145c6e720122942c00b8012bdb]
stable/5.15: [4837a192f6d06d5bb2f3f47d6ce5353ab69bf86b]
stable/5.4: [191d87a19cf1005ecf41e1ae08d74e17379e8391]
stable/6.1: [7562780e32b84196731d57dd24563546fcf6d082]

CVE-2023-52525: wifi: mwifiex: Fix oob check condition in
mwifiex_process_rx_packet

Announce: https://lore.kernel.org/linux-cve-announce/2024030254-CVE-2023-52525-3989@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

This CVE announce does not contain fixed commit in the mainline.
The commit aef7a030 ("wifi: mwifiex: Fix oob check condition in
mwifiex_process_rx_packet ") fixes in the mainline.
It's intdouced by commit 1195852 ("wifi: mwifiex: Fix OOB and integer
underflow when rx packets") in 6.6-rc1.

Fixed status
cip/4.4: [ad1e56ff6e81e312f70ab00930f7c85f0a69ee38]
cip/4.4-rt: [ad1e56ff6e81e312f70ab00930f7c85f0a69ee38]
cip/4.4-st: [ad1e56ff6e81e312f70ab00930f7c85f0a69ee38]
mainline: [aef7a0300047e7b4707ea0411dc9597cba108fc8]
stable/4.19: [16cc18b9080892d1a0200a38e36ae52e464bc555]
stable/5.10: [10a18c8bac7f60d32b7af22da03b66f350beee38]
stable/5.15: [5afb996349cb6d1f14d6ba9aaa7aed3bd82534f6]
stable/5.4: [b8e260654a29de872e7cb85387d8ab8974694e8e]
stable/6.1: [6b706286473db4fd54b5f869faa67f4a8cb18e99]

CVE-2023-52526: erofs: fix memory leak of LZMA global compressed deduplication

Announce: https://lore.kernel.org/linux-cve-announce/2024030254-CVE-2023-52526-8928@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 5c2a642 ("erofs: introduce partial-referenced
pclusters") in v6.1-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.6-rc5.

Fixed status
mainline: [75a5221630fe5aa3fedba7a06be618db0f79ba1e]
stable/6.1: [6a5a8f0a9740f865693d5aa97a42cc4504538e18]

CVE-2023-52527: ipv4, ipv6: Fix handling of transhdrlen in
__ip{,6}_append_data()

Announce: https://lore.kernel.org/linux-cve-announce/2024030254-CVE-2023-52527-a1e8@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit a32e0ee ("l2tp: introduce L2TPv3 IP encapsulation
support for IPv6") in v3.5-rc1.
Fixed in v6.6-rc5.

Fixed status
cip/4.4: [b4985ece59e38e3b46fa2c5a23fd73aae300999b]
cip/4.4-rt: [b4985ece59e38e3b46fa2c5a23fd73aae300999b]
cip/4.4-st: [b4985ece59e38e3b46fa2c5a23fd73aae300999b]
mainline: [9d4c75800f61e5d75c1659ba201b6c0c7ead3070]
stable/4.19: [559d697c5d072593d22b3e0bd8b8081108aeaf59]
stable/5.10: [96b2e1090397217839fcd6c9b6d8f5d439e705ed]
stable/5.15: [cd1189956393bf850b2e275e37411855d3bd86bb]
stable/5.4: [1fc793d68d50dee4782ef2e808913d5dd880bcc6]
stable/6.1: [f6a7182179c0ed788e3755ee2ed18c888ddcc33f]

CVE-2023-52528: net: usb: smsc75xx: Fix uninit-value access in
__smsc75xx_read_reg

Announce: https://lore.kernel.org/linux-cve-announce/2024030254-CVE-2023-52528-c33b@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit d0cad87 ("smsc75xx: SMSC LAN75xx USB gigabit
ethernet adapter driver") in v2.6.34-rc2.
Fixed in v6.6-rc5.

Fixed status
cip/4.4: [7149c409c334776ebfcca45f37ee98c723c87eed]
cip/4.4-rt: [7149c409c334776ebfcca45f37ee98c723c87eed]
cip/4.4-st: [7149c409c334776ebfcca45f37ee98c723c87eed]
mainline: [e9c65989920f7c28775ec4e0c11b483910fb67b8]
stable/4.19: [2a36d9e2995c8c3c3f179aab1215a69cff06cbed]
stable/5.10: [30bc4d7aebe33904b0f2d3aad4b4a9c6029ad0c5]
stable/5.15: [cda10784a176d7192f08ecb518f777a4e9575812]
stable/5.4: [310f1c92f65ad905b7e81fe14de82d979ebbd825]
stable/6.1: [9ffc5018020fe646795a8dc1203224b8f776dc09]

CVE-2023-52529: HID: sony: Fix a potential memory leak in sony_probe()

Announce: https://lore.kernel.org/linux-cve-announce/2024030255-CVE-2023-52529-56ff@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit fb1a79a ("HID: sony: fix freeze when inserting
ghlive ps3/wii dongles") in v5.14-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.6-rc5.

Fixed status
mainline: [e1cd4004cde7c9b694bbdd8def0e02288ee58c74]
stable/5.15: [bb0707fde7492121917fd9ddb43829e96ec0bb9e]
stable/6.1: [f237b17611fa3501f43f12d1cb64323e10fdcb4f]

CVE-2023-52530: wifi: mac80211: fix potential key use-after-free

Announce: https://lore.kernel.org/linux-cve-announce/2024030255-CVE-2023-52530-ebf0@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit fdf7cb4 ("mac80211: accept key reinstall without
changing anything") in v4.14-rc6.
This commit is not backported to older stable kernels.
Fixed in v6.6-rc5.

Fixed status
mainline: [31db78a4923ef5e2008f2eed321811ca79e7f71b]
stable/6.1: [2f4e16e39e4f5e78248dd9e51276a83203950b36]

CVE-2023-52531: wifi: iwlwifi: mvm: Fix a memory corruption issue

Announce: https://lore.kernel.org/linux-cve-announce/2024030255-CVE-2023-52531-be21@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 8ca151b ("iwlwifi: add the MVM driver") in v3.9-rc1.
Fixed in v6.6-rc5.

Fixed status
mainline: [8ba438ef3cacc4808a63ed0ce24d4f0942cfe55d]
stable/5.15: [7c8faa31080342aec4903c9acb20caf82fcca1ef]
stable/6.1: [6b3223449c959a8be94a1f042288059e40fcccb0]

CVE-2023-52532: net: mana: Fix TX CQE error handling

Announce: https://lore.kernel.org/linux-cve-announce/2024030255-CVE-2023-52532-57db@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit ca9c54d ("net: mana: Add a driver for Microsoft
Azure Network Adapter (MANA)") in v5.13-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.6-rc5.

Fixed status
mainline: [b2b000069a4c307b09548dc2243f31f3ca0eac9c]
stable/6.1: [b67d7b1bfc46d05c1a58b172516454698e8d5004]

CVE-2023-52559: iommu/vt-d: Avoid memory allocation in iommu_suspend()

Announce: https://lore.kernel.org/linux-cve-announce/2024030252-CVE-2023-52559-680e@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 33e0715 ("iommu/vt-d: Avoid GFP_ATOMIC where it
is not needed") in v5.11-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.6-rc5.

Fixed status
mainline: [59df44bfb0ca4c3ee1f1c3c5d0ee8e314844799e]
stable/5.15: [29298c85a81abdc512e87537515ed4b1a9601d0e]
stable/6.1: [c12ef025add77ca3a0902e8719d552b6d47b4282]

CVE-2023-52560: mm/damon/vaddr-test: fix memory leak in
damon_do_test_apply_three_regions()

Announce: https://lore.kernel.org/linux-cve-announce/2024030252-CVE-2023-52560-c3de@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 9f86d62 ("mm/damon/vaddr-test: remove unnecessary
variables") in v5.16-rc5.
This commit is not backported to older stable kernels.
Fixed in v6.6-rc4.

Fixed status
mainline: [45120b15743fa7c0aa53d5db6dfb4c8f87be4abd]
stable/6.1: [9a4fe81a8644b717d57d81ce5849e16583b13fe8]

CVE-2023-52561: arm64: dts: qcom: sdm845-db845c: Mark cont splash
memory region as reserved

Announce: https://lore.kernel.org/linux-cve-announce/2024030253-CVE-2023-52561-89b2@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.6-rc1.
The sdm845-db845c.dts is introduced by commit 3f72e2d3 in ("arm64:
dts: qcom: Add Dragonboard 845c")

Fixed status
mainline: [110e70fccce4f22b53986ae797d665ffb1950aa6]
stable/6.1: [dc1ab6577475b0460ba4261cd9caec37bd62ca0b]

CVE-2023-52562: mm/slab_common: fix slab_caches list corruption after
kmem_cache_destroy()

Announce: https://lore.kernel.org/linux-cve-announce/2024030253-CVE-2023-52562-da24@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 0495e33 ("mm/slab_common: Deleting kobject in
kmem_cache_destroy() without holding slab_mutex/cpu_hotplug_lock") in
v6.0-rc4.
This commit is not backported to older stable kernels.
Fixed in v6.6-rc4.

Fixed status
mainline: [46a9ea6681907a3be6b6b0d43776dccc62cad6cf]
stable/6.1: [a5569bb187521432f509b69dda7d29f78b2d38b0]

CVE-2023-52563: drm/meson: fix memory leak on ->hpd_notify callback

Announce: https://lore.kernel.org/linux-cve-announce/2024030253-CVE-2023-52563-269f@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 0af5e0b ("drm/meson: encoder_hdmi: switch to
bridge DRM_BRIDGE_ATTACH_NO_CONNECTOR") in v5.17-rc1.
This commit is backported to 5.15. Linux 4.4, 4.19, 5.4, 5.10 are not affected.
Fixed in v6.6-rc3.

Fixed status
mainline: [099f0af9d98231bb74956ce92508e87cbcb896be]
stable/5.15: [66cb6d74f5a1b6eafe3370b56bf2cb575a91acbc]
stable/6.1: [ee335e0094add7fc2c7034e0534e1920d61d2078]

CVE-2023-52564: Revert "tty: n_gsm: fix UAF in gsm_cleanup_mux"

Announce: https://lore.kernel.org/linux-cve-announce/2024030253-CVE-2023-52564-88cb@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 9b9c819 ("tty: n_gsm: fix UAF in
gsm_cleanup_mux") in v6.5-rc4.
This commit is backported to 5.10 and 5.15. Linux 4.x and 5.4 are not affected.
Fixed in v6.6-rc4.

Fixed status
mainline: [29346e217b8ab8a52889b88f00b268278d6b7668]
stable/5.10: [6d5c8862932d31a810b6545f7d69ecc124402c6e]
stable/5.15: [a48d2bcd23f2c98d575bc2f9b7a3fbd16aeea9eb]
stable/6.1: [c61d0b87a7028c2c10faffc524d748334c7b9827]

CVE-2023-52565: media: uvcvideo: Fix OOB read

Announce: https://lore.kernel.org/linux-cve-announce/2024030254-CVE-2023-52565-07ce@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 40140ed ("media: uvcvideo: Implement mask for
V4L2_CTRL_TYPE_MENU") in v6.3-rc1.
This commit is backported to 6.1. Linux 4.x and 5.x are not affected.
Fixed in v6.6-rc3.

Fixed status
mainline: [41ebaa5e0eebea4c3bac96b72f9f8ae0d77c0bdb]
stable/6.1: [09635bf4cdd4adf2160198a6041bcc7ca46c0558]

CVE-2023-52566: nilfs2: fix potential use after free in
nilfs_gccache_submit_read_data()

Announce: https://lore.kernel.org/linux-cve-announce/2024030254-CVE-2023-52566-69f0@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit a3d93f7 ("nilfs2: block cache for garbage
collection") in v2.6.30-rc1.
Fixed in v6.6-rc4.

Fixed status
cip/4.4: [d8accb5f4e874863faddb26bf353c2f0ec55ca56]
cip/4.4-rt: [d8accb5f4e874863faddb26bf353c2f0ec55ca56]
cip/4.4-st: [d8accb5f4e874863faddb26bf353c2f0ec55ca56]
mainline: [7ee29facd8a9c5a26079148e36bcf07141b3a6bc]
stable/4.19: [bb61224f6abc8e71bfdf06d7c984e23460875f5b]
stable/5.10: [7130a87ca32396eb9bf48b71a2d42259ae44c6c7]
stable/5.15: [3936e8714907cd55e37c7cc50e50229e4a9042e8]
stable/5.4: [193b5a1c6c67c36b430989dc063fe7ea4e200a33]
stable/6.1: [980663f1d189eedafd18d80053d9cf3e2ceb5c8c]

CVE-2023-52567: serial: 8250_port: Check IRQ data before use

Announce: https://lore.kernel.org/linux-cve-announce/2024030254-CVE-2023-52567-38c1@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 0ba9e3a ("serial: 8250: Add missing wakeup event
reporting") in v6.4-rc1.
This commit is backpoted to older stable kernels.
Fixed in v6.6-rc4.

Fixed status
cip/4.4: [0d4146285759cd38fed112642796da6bec255548]
cip/4.4-rt: [0d4146285759cd38fed112642796da6bec255548]
cip/4.4-st: [0d4146285759cd38fed112642796da6bec255548]
mainline: [cce7fc8b29961b64fadb1ce398dc5ff32a79643b]
stable/4.19: [c334650150c29234b0923476f51573ae1b2f252a]
stable/5.10: [e14afa4450cb7e4cf93e993a765801203d41d014]
stable/5.15: [2b837f13a818f96304736453ac53b66a70aaa4f2]
stable/5.4: [bf3c728e3692cc6d998874f0f27d433117348742]
stable/6.1: [e14f68a48fd445a083ac0750fafcb064df5f18f7]

CVE-2023-52568: x86/sgx: Resolves SECS reclaim vs. page fault for EAUG race

Announce: https://lore.kernel.org/linux-cve-announce/2024030255-CVE-2023-52568-b5c6@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 5a90d2c ("x86/sgx: Support adding of pages to an
initialized enclave") in v6.0-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.6-rc4.

Fixed status
mainline: [c6c2adcba50c2622ed25ba5d5e7f05f584711358]
stable/6.1: [811ba2ef0cb6402672e64ba1419d6ef95aa3405d]

CVE-2023-52569: btrfs: remove BUG() after failure to insert delayed
dir index item

Announce: https://lore.kernel.org/linux-cve-announce/2024030255-CVE-2023-52569-a9c1@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.6-rc2.

Fixed status
mainline: [2c58c3931ede7cd08cbecf1f1a4acaf0a04a41a9]
stable/6.1: [39c4a9522db0072570d602e9b365119e17fb9f4f]

CVE-2023-52570: vfio/mdev: Fix a null-ptr-deref bug for mdev_unregister_parent()

Announce: https://lore.kernel.org/linux-cve-announce/2024030255-CVE-2023-52570-0789@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit da44c34 ("vfio/mdev: simplify mdev_type
handling") in v6.1-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.6-rc4.

Fixed status
mainline: [c777b11d34e0f47dbbc4b018ef65ad030f2b283a]
stable/6.1: [c01b2e0ee22ef8b4dd7509a93aecc0ac0826bae4]

CVE-2023-52571: power: supply: rk817: Fix node refcount leak

Announce: https://lore.kernel.org/linux-cve-announce/2024030255-CVE-2023-52571-087e@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 54c03bf ("power: supply: Fix refcount leak in
rk817_charger_probe") in v6.2-rc1.
This commit is backported to 6.1. Linux 4.x and 5.x are not affected.
Fixed in v6.6-rc4.

Fixed status
mainline: [488ef44c068e79752dba8eda0b75f524f111a695]
stable/6.1: [fe6406238d5a24e9fb0286c71edd67b99d8db58d]

CVE-2023-52572: cifs: Fix UAF in cifs_demultiplex_thread()

Announce: https://lore.kernel.org/linux-cve-announce/2024030256-CVE-2023-52572-2b92@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit ec637e3 ("[CIFS] Avoid extra large buffer
allocation (and memcpy) in cifs_readpages") in v2.6.20.16.
Fixed in v6.6-rc3.

Fixed status
mainline: [d527f51331cace562393a8038d870b3e9916686f]
stable/6.1: [908b3b5e97d25e879de3d1f172a255665491c2c3]

CVE-2023-52573: net: rds: Fix possible NULL-pointer dereference

Announce: https://lore.kernel.org/linux-cve-announce/2024030256-CVE-2023-52573-531c@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit fd261ce ("rds: rdma: update rdma transport for
tos") in v5.1-rc1.
This commit is not backported to 4.x kernels.
Fixed in v6.6-rc3.

Fixed status
mainline: [f1d95df0f31048f1c59092648997686e3f7d9478]
stable/5.10: [f515112e833791001aaa8ab886af3ca78503617f]
stable/5.15: [ea82139e6e3561100d38d14401d57c0ea93fc07e]
stable/5.4: [812da2a08dc5cc75fb71e29083ea20904510ac7a]
stable/6.1: [51fa66024a5eabf270164f2dc82a48ffb35a12e9]

CVE-2023-52574: team: fix null-ptr-deref when team device type is changed

Announce: https://lore.kernel.org/linux-cve-announce/2024030256-CVE-2023-52574-a423@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 1d76efe ("team: add support for non-ethernet
devices") in v3.7-rc1.
Fixed in v6.6-rc3.

Fixed status
mainline: [492032760127251e5540a5716a70996bacf2a3fd]
stable/4.19: [a7fb47b9711101d2405b0eb1276fb1f9b9b270c7]
stable/5.10: [b44dd92e2afd89eb6e9d27616858e72a67bdc1a7]
stable/5.15: [cd05eec2ee0cc396813a32ef675634e403748255]
stable/5.4: [c5f6478686bb45f453031594ae19b6c9723a780d]
stable/6.1: [2f0acb0736ecc3eb85dc80ad2790d634dcb10b58]

CVE-2023-52575: x86/srso: Fix SBPB enablement for spec_rstack_overflow=off

Announce: https://lore.kernel.org/linux-cve-announce/2024030256-CVE-2023-52575-34bf@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit fb3bd91 ("x86/srso: Add a Speculative RAS
Overflow mitigation") in v6.5-rc6.
Fixed in v6.6-rc3.

According to the CVE announce, this CVE is introcued by commit fb3bd914b3ec.

```
    Issue introduced in 5.10.189 with commit 8457fb5740b1 and fixed in
5.10.198 with commit ae806c74c063
    Issue introduced in 5.15.125 with commit 153f9a7b02d4 and fixed in
5.15.134 with commit 13ea4b92e875
    Issue introduced in 6.1.44 with commit 4f25355540ad and fixed in
6.1.56 with commit adbcec23c842
    Issue introduced in 6.5 with commit fb3bd914b3ec and fixed in
6.5.6 with commit e3cb8b2c391b
    Issue introduced in 6.5 with commit fb3bd914b3ec and fixed in 6.6
with commit 01b057b2f4cc
```

However, 5.10, 5.15, and 6.1 show different subject from fb3bd914b3ec.

$ git log -n 1 --pretty=oneline fb3bd914b3ec
fb3bd914b3ec28f5fb697ac55c4846ac2d542855 x86/srso: Add a Speculative
RAS Overflow mitigation
$ git log -n 1 --pretty=oneline 4f25355540ad
4f25355540ad4d40dd3445f66159a321dad29cc8 x86/srso: Tie SBPB bit
setting to microcode patch detection
$ git log -n 1 --pretty=oneline 153f9a7b02d4
153f9a7b02d4f292671e81077e901ef01e123a9f x86/srso: Tie SBPB bit
setting to microcode patch detection
$ git log -n 1 --pretty=oneline 8457fb5740b1
8457fb5740b14311a8941044ff4eb5a3945de9b2 x86/srso: Tie SBPB bit
setting to microcode patch detection

Fixed status
mainline: [01b057b2f4cc2d905a0bd92195657dbd9a7005ab]
stable/5.10: [ae806c74c0634b0c23855066d8ba28d850fd1260]
stable/5.15: [13ea4b92e8759d2f6c330a73cde31ad9c313021b]
stable/6.1: [adbcec23c8423e3d5df1839c5ae91599dcf703cb]

CVE-2023-52576: x86/mm, kexec, ima: Use memblock_free_late() from
ima_free_kexec_buffer()

Announce: https://lore.kernel.org/linux-cve-announce/2024030257-CVE-2023-52576-7ee2@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit fee3ff9 ("powerpc: Move arch independent ima
kexec functions to drivers/of/kexec.c") in v5.13-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.6-rc3.

Fixed status
mainline: [34cf99c250d5cd2530b93a57b0de31d3aaf8685b]
stable/6.1: [eef16bfdb212da60f5144689f2967fb25b051a2b]

CVE-2023-52577: dccp: fix dccp_v4_err()/dccp_v6_err() again

Announce: https://lore.kernel.org/linux-cve-announce/2024030257-CVE-2023-52577-2638@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

This CVE announce does not contain fixed commit in the mainline.
The commit 6af2897 ("dccp: fix dccp_v4_err()/dccp_v6_err() again")
fixes mainline in 6.6-rc3.
Introduced by commit 977ad86 ("dccp: Fix out of bounds access in DCCP
error handler") in 6.6-rc1.

Fixed status
cip/4.4: [f775702709181d2ffc5047ec9b6bab3e8642f01c]
cip/4.4-rt: [f775702709181d2ffc5047ec9b6bab3e8642f01c]
cip/4.4-st: [f775702709181d2ffc5047ec9b6bab3e8642f01c]
mainline: [6af289746a636f71f4c0535a9801774118486c7a]
stable/4.19: [62c218124fe58372e0e1f60d5b634d21c264b337]
stable/5.10: [60d73c62e3e4464f375758b6f2459c13d46465b6]
stable/5.15: [26df9ab5de308caa1503d937533c56c35793018d]
stable/5.4: [a6f4d582e25d512c9b492670b6608436694357b3]
stable/6.1: [73be49248a04746096339a48a33fa2f03bd85969]

CVE-2023-52578: net: bridge: use DEV_STATS_INC()

Announce: https://lore.kernel.org/linux-cve-announce/2024030257-CVE-2023-52578-50cb@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 1c29fc4 ("[BRIDGE]: keep track of received
multicast packets") in v2.6.20.16.
Fixed in v6.6-rc3.

Fixed status
mainline: [44bdb313da57322c9b3c108eb66981c6ec6509f4]
stable/4.19: [d2346e6beb699909ca455d9d20c4e577ce900839]
stable/5.10: [04cc361f029c14dd067ad180525c7392334c9bfd]
stable/5.15: [8bc97117b51d68d5cea8f5351cca2d8c4153f394]
stable/5.4: [ad8d39c7b437fcdab7208a6a56c093d222c008d5]
stable/6.1: [89f9f20b1cbd36d99d5a248a4bf8d11d4fd049a2]

CVE-2023-52579: ipv4: fix null-deref in ipv4_link_failure

Announce: https://lore.kernel.org/linux-cve-announce/2024030257-CVE-2023-52579-af56@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

This CVE is rejected.
Introduced by commit ed0de45 ("ipv4: recompile ip options in
ipv4_link_failure") in v5.1-rc6.
This commit is backported to older stable kernels.
Fixed in v6.6-rc3.

Fixed status
cip/4.4: [d4dccc15764f93278855862b35259fc62b50540e]
cip/4.4-rt: [d4dccc15764f93278855862b35259fc62b50540e]
cip/4.4-st: [d4dccc15764f93278855862b35259fc62b50540e]
mainline: [0113d9c9d1ccc07f5a3710dac4aa24b6d711278c]
stable/4.19: [a2cf7bd75b3992e8df68dd5fdc6499b67d45f6e0]
stable/5.10: [8689c9ace976d6c078e6dc844b09598796e84099]
stable/5.15: [8860d354f653628b6330e1c5b06b2828948135a4]
stable/5.4: [810fd23d9715474aa27997584e8fc9396ef3cb67]
stable/6.1: [2712545e535d7a2e4c53b9c9658a9c88c6055862]

CVE-2023-52580: net/core: Fix ETH_P_1588 flow dissector

Announce: https://lore.kernel.org/linux-cve-announce/2024030258-CVE-2023-52580-c37e@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 4f1cc51 ("net: flow_dissector: Parse PTP L2
packet header") in v5.12-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.6-rc3.

Fixed status
mainline: [75ad80ed88a182ab2ad5513e448cf07b403af5c3]
stable/5.15: [f90a7b9586d72f907092078a9f394733ca502cc9]
stable/6.1: [488ea2a3e2666022f79abfdd7d12e8305fc27a40]

CVE-2023-52581: netfilter: nf_tables: fix memleak when more than 255
elements expired

Announce: https://lore.kernel.org/linux-cve-announce/2024030258-CVE-2023-52581-2165@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 5f68718 ("netfilter: nf_tables: GC transaction
API to avoid race with control plane") in v6.5-rc6.
This commit is backported to 6.1 and 5.x kernels. Linux 4.x is not affected.
Fixed in v6.6-rc3.

Fixed status
mainline: [cf5000a7787cbc10341091d37245a42c119d26c5]
stable/5.10: [09c85f2d21ab6b5acba31a037985b13e8e6565b8]
stable/5.15: [ef99506eaf1dc31feff1adfcfd68bc5535a22171]
stable/5.4: [a995a68e8a3b48533e47c856865d109a1f1a9d01]
stable/6.1: [7e5d732e6902eb6a37b35480796838a145ae5f07]

CVE-2023-52582: netfs: Only call folio_start_fscache() one time for each folio

Announce: https://lore.kernel.org/linux-cve-announce/2024030258-CVE-2023-52582-07c8@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 3d3c950 ("netfs: Provide readahead and readpage
netfs helpers") in v5.13-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.6-rc3.

Fixed status
mainline: [df1c357f25d808e30b216188330e708e09e1a412]
stable/6.1: [df9950d37df113db59495fa09d060754366a2b7c]

CVE-2024-26621: mm: huge_memory: don't force huge page alignment on 32 bit

Announce: https://lore.kernel.org/linux-cve-announce/2024030255-CVE-2024-26621-9300@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit efa7df3 ("mm: align larger anonymous mappings on
THP boundaries") in v6.7.
This commit is not backported to older stable kernels
Fixed in v6.8-rc3.

Fixed status
mainline: [4ef9ad19e17676b9ef071309bc62020e2373705d]
stable/6.1: [87632bc9ecff5ded93433bc0fca428019bdd1cfe]
stable/6.7: [7432376c913381c5f24d373a87ff629bbde94b47]

CVE-2024-26622: tomoyo: fix UAF write bug in tomoyo_write_control()

Announce: https://lore.kernel.org/linux-cve-announce/2024030409-CVE-2024-26622-9e01@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit bd03a3e ("TOMOYO: Add policy namespace support.")
in v3.1-rc1.
Fixed in v6.8-rc7.

Fixed status
mainline: [2f03fc340cac9ea1dc63cbf8c93dd2eb0f227815]
stable/5.10: [a23ac1788e2c828c097119e9a3178f0b7e503fee]
stable/5.15: [7d930a4da17958f869ef679ee0e4a8729337affc]
stable/6.1: [3bfe04c1273d30b866f4c7c238331ed3b08e5824]
stable/6.6: [2caa605079488da9601099fbda460cfc1702839f]
stable/6.7: [6edefe1b6c29a9932f558a898968a9fcbeec5711]

CVE-2021-47082: tun: avoid double free in tun_free_netdev

Announce: https://lore.kernel.org/linux-cve-announce/2024030451-CVE-2021-47082-b12c@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v5.16-rc7.
It seems as if Linux 4.4 may be affected.

Fixed status
mainline: [158b515f703e75e7d68289bf4d98c664e1d632df]
stable/4.19: [8eb43d635950e27c29f1e9e49a23b31637f37757]
stable/5.10: [a01a4e9f5dc93335c716fa4023b1901956e8c904]
stable/5.15: [3cb5ae77799e8ed6ec3fec0b6b4cd07f01650cc5]
stable/5.4: [0c0e566f0387490d16f166808c72e9c772027681]

CVE-2021-47083: pinctrl: mediatek: fix global-out-of-bounds issue

Announce: https://lore.kernel.org/linux-cve-announce/2024030454-CVE-2021-47083-eab5@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v5.16-rc7.
It seems as if commit fb5fa8dc1 ("pinctrl: mediatek: extend struct
mtk_pin_desc to pinctrl-mtk-common-v2.c") in 4.20-rc1 introduced this
bug.
The commit fb5fa8dc1 is not backported to older stable kernels.

Fixed status
mainline: [2d5446da5acecf9c67db1c9d55ae2c3e5de01f8d]
stable/5.10: [441d3873664d170982922c5d2fc01fa89d9439ed]
stable/5.15: [fb563baa3eb8e7a15f2cff3c2695e2cca0493e69]
stable/5.4: [f373298e1bf0c6ea097c0bcc558dc43ad53e421f]

CVE-2021-47084: hamradio: defer ax25 kfree after unregister_netdev

Announce: https://lore.kernel.org/linux-cve-announce/2024030455-CVE-2021-47084-4984@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v5.16-rc1.
All stable kernels have been fixed.

Fixed status
cip/4.4: [b5b193d0c67180fefdc664650138e3b7959df615]
cip/4.4-rt: [b5b193d0c67180fefdc664650138e3b7959df615]
cip/4.4-st: [b5b193d0c67180fefdc664650138e3b7959df615]
mainline: [3e0588c291d6ce225f2b891753ca41d45ba42469]
stable/4.19: [896193a02a2981e60c40d4614fd095ce92135ccd]
stable/4.4: [b5b193d0c67180fefdc664650138e3b7959df615]
stable/5.10: [450121075a6a6f1d50f97225d3396315309d61a1]
stable/5.15: [cb6c99aedd2c843056a598a8907a6128cb07603b]
stable/5.4: [ef5f7bfa19e3fc366f4c6d1a841ceaddf7a9f5d4]

CVE-2021-47085: hamradio: improve the incomplete fix to avoid NPD

Announce: https://lore.kernel.org/linux-cve-announce/2024030455-CVE-2021-47085-3c44@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v5.16-rc7.
All stable kernels have been fixed.

Fixed status
cip/4.4: [371a874ea06f147d6ca30be43dad33683965eba6]
cip/4.4-rt: [371a874ea06f147d6ca30be43dad33683965eba6]
cip/4.4-st: [371a874ea06f147d6ca30be43dad33683965eba6]
mainline: [b2f37aead1b82a770c48b5d583f35ec22aabb61e]
stable/4.19: [b68f41c6320b2b7fbb54a95f07a69f3dc7e56c59]
stable/4.4: [371a874ea06f147d6ca30be43dad33683965eba6]
stable/5.10: [7dd52af1eb5798f590d9d9e1c56ed8f5744ee0ca]
stable/5.15: [03d00f7f1815ec00dab5035851b3de83afd054a8]
stable/5.4: [a5c6a13e9056d87805ba3042c208fbd4164ad22b]

CVE-2021-47086: phonet/pep: refuse to enable an unbound pipe

Announce: https://lore.kernel.org/linux-cve-announce/2024030455-CVE-2021-47086-cdaa@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v5.16-rc7.
All stable kernels have been fixed.

Fixed status
cip/4.4: [0bbdd62ce9d44f3a22059b3d20a0df977d9f6d59]
cip/4.4-rt: [0bbdd62ce9d44f3a22059b3d20a0df977d9f6d59]
cip/4.4-st: [0bbdd62ce9d44f3a22059b3d20a0df977d9f6d59]
mainline: [75a2f31520095600f650597c0ac41f48b5ba0068]
stable/4.19: [982b6ba1ce626ef87e5c29f26f2401897554f235]
stable/4.4: [0bbdd62ce9d44f3a22059b3d20a0df977d9f6d59]
stable/5.10: [52ad5da8e316fa11e3a50b3f089aa63e4089bf52]
stable/5.15: [53ccdc73eedaf0e922c45b569b797d2796fbaafa]
stable/5.4: [48c76fc53582e7f13c1e0b11c916e503256c4d0b]

CVE-2021-47087: tee: optee: Fix incorrect page free bug

Announce: https://lore.kernel.org/linux-cve-announce/2024030413-CVE-2021-47087-4132@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit ec185dd ("optee: Fix memory leak when failing to
register shm pages") in v5.14-rc5.
This commit is not backported to 4.x kernels.
Fixed in v5.16-rc7.

Fixed status
mainline: [18549bf4b21c739a9def39f27dcac53e27286ab5]
stable/5.10: [ad338d825e3f7b96ee542bf313728af2d19fe9ad]
stable/5.15: [91e94e42f6fc49635f1a16d8ae3f79552bcfda29]
stable/5.4: [806142c805cacd098e61bdc0f72c778a2389fe4a]

CVE-2021-47088: mm/damon/dbgfs: protect targets destructions with kdamond_lock

Announce: https://lore.kernel.org/linux-cve-announce/2024030413-CVE-2021-47088-269c@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 4bc0595 ("mm/damon: implement a debugfs-based
user space interface") in v5.15-rc1.
This commit is not backported to older stable kernel.
Fixed in v5.16-rc7.

Fixed status
mainline: [34796417964b8d0aef45a99cf6c2d20cebe33733]
stable/5.15: [330c6117a82c16a9a365a51cec5c9ab30b13245c]

CVE-2021-47089: kfence: fix memory leak when cat kfence objects

Announce: https://lore.kernel.org/linux-cve-announce/2024030413-CVE-2021-47089-bc5a@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 0ce20dd ("mm: add Kernel Electric-Fence
infrastructure") in v5.12-rc1.
This commit is not backported to older stable kernel.
Fixed in v5.16-rc7.

Fixed status
mainline: [0129ab1f268b6cf88825eae819b9b84aa0a85634]
stable/5.15: [2f06c8293d27f6337f907042c602c9c953988c48]

CVE-2021-47090: mm/hwpoison: clear MF_COUNT_INCREASED before retrying
get_any_page()

Announce: https://lore.kernel.org/linux-cve-announce/2024030413-CVE-2021-47090-a429@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit b94e028 ("mm,hwpoison: try to narrow window race
for free pages") in v5.10-rc1.
This commit is not backported to older stable kernel.
Fixed in v5.16-rc7.

Fixed status
mainline: [2a57d83c78f889bf3f54eede908d0643c40d5418]
stable/5.10: [1f207076740101fed87074a6bc924dbe806f08a5]
stable/5.15: [c691e7575eff76e563b0199c23ec46bd454f43e3]

CVE-2021-47091: mac80211: fix locking in ieee80211_start_ap error path

Announce: https://lore.kernel.org/linux-cve-announce/2024030414-CVE-2021-47091-edad@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 295b02c ("mac80211: Add FILS discovery support")
in v5.10-rc1.
This commit is not backported to older stable kernel.
Fixed in v5.16-rc7.

Fixed status
mainline: [87a270625a89fc841f1a7e21aae6176543d8385c]
stable/5.10: [ac61b9c6c0549aaeb98194cf429d93c41bfe5f79]
stable/5.15: [c1d1ec4db5f7264cfc21993e59e8f2dcecf4b44f]

CVE-2021-47092: KVM: VMX: Always clear vmx->fail on emulation_required

Announce: https://lore.kernel.org/linux-cve-announce/2024030414-CVE-2021-47092-36e2@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit c8607e4 ("KVM: x86: nVMX: don't fail nested VM
entry on invalid guest state if !from_vmentry") in v5.15-rc4.
This commit is not backported to older stable kernel.
Fixed in v5.16-rc7.

Fixed status
mainline: [a80dfc025924024d2c61a4c1b8ef62b2fce76a04]
stable/5.15: [e4e4e7cb229821cd215031abc47efdab5486a67c]

CVE-2021-47093: platform/x86: intel_pmc_core: fix memleak on
registration failure

Announce: https://lore.kernel.org/linux-cve-announce/2024030414-CVE-2021-47093-ccd0@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 938835a ("platform/x86: intel_pmc_core: do not
create a static struct device") in v5.9.
This commit is not backported to older stable kernel.
Fixed in v5.16-rc7.

Fixed status
mainline: [26a8b09437804fabfb1db080d676b96c0de68e7c]
stable/5.10: [7a37f2e370699e2feca3dca6c8178c71ceee7e8a]
stable/5.15: [9ca1324755f1f8629a370af5cc315b175331f5d1]

CVE-2021-47094: KVM: x86/mmu: Don't advance iterator after restart due
to yielding

Announce: https://lore.kernel.org/linux-cve-announce/2024030414-CVE-2021-47094-8cc7@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit faaf05b ("kvm: x86/mmu: Support zapping SPTEs in
the TDP MMU") in v5.10-rc1.
Introduced by commit 1af4a96 ("KVM: x86/mmu: Yield in TDU MMU iter
even if no SPTES changed") in v5.12-rc1.
These commits are not backported to older stable kernel.
Fixed in v5.16-rc7.

Fixed status
mainline: [3a0f64de479cae75effb630a2e0a237ca0d0623c]
stable/5.15: [d884eefd75cc54887bc2e9e724207443525dfb2c]

CVE-2021-47095: ipmi: ssif: initialize ssif_info->client early

Announce: https://lore.kernel.org/linux-cve-announce/2024030414-CVE-2021-47095-39dd@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit c4436c9 ("ipmi_ssif: avoid registering duplicate
ssif interface") in v5.4-rc1.
This commit is not backported to older stable kernel.
Fixed in v5.16-rc7.

Fixed status
mainline: [34f35f8f14bc406efc06ee4ff73202c6fd245d15]
stable/5.10: [1f6ab847461ce7dd89ae9db2dd4658c993355d7c]
stable/5.15: [77a7311ca167aa5b7055c549a940a56e73ee5f29]
stable/5.4: [8efd6a3391f7b0b19fb0c38e50add06ca30c94af]

CVE-2021-47096: ALSA: rawmidi - fix the uninitalized user_pversion

Announce: https://lore.kernel.org/linux-cve-announce/2024030415-CVE-2021-47096-40c7@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 09d2317 ("ALSA: rawmidi: introduce
SNDRV_RAWMIDI_IOCTL_USER_PVERSION") in v5.15-rc4.
This commit is not backported to older stable kernel.
Fixed in v5.16-rc7.

Fixed status
mainline: [39a8fc4971a00d22536aeb7d446ee4a97810611b]
stable/5.15: [b398fcbe4de1e1100867fdb6f447c6fbc8fe7085]

CVE-2021-47097: Input: elantech - fix stack out of bound access in
elantech_change_report_id()

Announce: https://lore.kernel.org/linux-cve-announce/2024030415-CVE-2021-47097-e7f4@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit e4c9062 ("Input: elantech - fix protocol errors
for some trackpoints in SMBus mode") in v5.11-rc1.
This commit is backported to 5.10 and 5.4. Linux 4.x is not affected.
Fixed in v5.16-rc7.

Fixed status
mainline: [1d72d9f960ccf1052a0630a68c3d358791dbdaaa]
stable/5.10: [676c572439e58b7ee6b7ca3f1e5595382921045c]
stable/5.15: [dfd5b60b5342b6b505a104e48f08ad9b9bdbbd7b]
stable/5.4: [a7f95328c6f0afffdc4555f16e3bbab8bbf0d9be]

CVE-2021-47098: hwmon: (lm90) Prevent integer overflow/underflow in
hysteresis calculations

Announce: https://lore.kernel.org/linux-cve-announce/2024030415-CVE-2021-47098-e11f@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit b50aa49 ("hwmon: (lm90) Prevent integer
underflows of temperature calculations") in v5.14-rc1.
This commit is not backported to older stable kernel.
Fixed in v5.16-rc7.

Fixed status
mainline: [55840b9eae5367b5d5b29619dc2fb7e4596dba46]
stable/5.15: [d105f30bea9104c590a9e5b495cb8a49bdfe405f]

CVE-2021-47099: veth: ensure skb entering GRO are not cloned.

Announce: https://lore.kernel.org/linux-cve-announce/2024030415-CVE-2021-47099-3127@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit d3256ef ("veth: allow enabling NAPI even without
XDP") in v5.13-rc1.
This commit is not backported to older stable kernel.
Fixed in v5.16-rc7.

Fixed status
mainline: [9695b7de5b4760ed22132aca919570c0190cb0ce]
stable/5.15: [d2269ae48598e05b59ec9ea9e6e44fd33941130d]

CVE-2021-47100: ipmi: Fix UAF when uninstall ipmi_si and ipmi_msghandler module

Announce: https://lore.kernel.org/linux-cve-announce/2024030415-CVE-2021-47100-043d@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit b2cfd8a ("ipmi: Rework device id and guid
handling to catch changing BMCs") in v4.15-rc1.
Linux 4.4 is not affected.
Fixed in v5.16-rc7.

Fixed status
mainline: [ffb76a86f8096a8206be03b14adda6092e18e275]
stable/4.19: [925229d552724e1bba1abf01d3a0b1318539b012]
stable/5.10: [6809da5185141e61401da5b01896b79a4deed1ad]
stable/5.15: [6b3f7e4b10f343f05b5fb513b07a9168fbf1172e]
stable/5.4: [992649b8b16843d27eb39ceea5f9cf85ffb50a18]

CVE-2021-47101: asix: fix uninit-value in asix_mdio_read()

Announce: https://lore.kernel.org/linux-cve-announce/2024030415-CVE-2021-47101-f3fa@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit d9fe64e ("net: asix: Add in_pm parameter") in v4.9-rc1.
Linux 4.4 is not affected.
Fixed in v5.16-rc7.

Fixed status
mainline: [8035b1a2a37a29d8c717ef84fca8fe7278bc9f03]
stable/5.15: [d259f621c85949f30cc578cac813b82bb5169f56]

CVE-2021-47102: net: marvell: prestera: fix incorrect structure access

Announce: https://lore.kernel.org/linux-cve-announce/2024030416-CVE-2021-47102-1335@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 3d5048c ("net: marvell: prestera: move netdev
topology validation to prestera_main") in v5.14-rc1.
This commit is not backported to older stable kernels.
Fixed in v5.16-rc7.

Fixed status
mainline: [2efc2256febf214e7b2bdaa21fe6c3c3146acdcb]
stable/5.15: [5c553a0cd1263e4da5f220d80fa713fc3959c1d0]

CVE-2021-47103: inet: fully convert sk->sk_rx_dst to RCU rules

Announce: https://lore.kernel.org/linux-cve-announce/2024030416-CVE-2021-47103-4314@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 41063e9 ("ipv4: Early TCP socket demux.") in v3.6-rc1.
Fixed in v5.16-rc7. All stable kernels have been fixed.

Fixed status
cip/4.4: [f3d7398a12be2ec4ed01351025933af051d2cd6d]
cip/4.4-rt: [f3d7398a12be2ec4ed01351025933af051d2cd6d]
cip/4.4-st: [f3d7398a12be2ec4ed01351025933af051d2cd6d]
mainline: [8f905c0e7354ef261360fb7535ea079b1082c105]
stable/4.19: [75a578000ae5e511e5d0e8433c94a14d9c99c412]
stable/5.10: [f039b43cbaea5e0700980c2f0052da05a70782e0]
stable/5.15: [0249a4b8a554f2eb6a27b62516fa50168584faa4]
stable/5.4: [c3bb4a7e8cbc984e1cdac0fe6af60e880214ed6e]

CVE-2021-47104: IB/qib: Fix memory leak in qib_user_sdma_queue_pkts()

Announce: https://lore.kernel.org/linux-cve-announce/2024030444-CVE-2021-47104-bedc@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit d39bf40 ("IB/qib: Protect from buffer overflow in
struct qib_user_sdma_pkt fields") in v5.15.
Fixed in v5.16-rc7. All stable kernels have been fixed.

Fixed status
cip/4.4: [1ced0a3015a95c6a6db45e37250912c4c86697ab]
cip/4.4-rt: [1ced0a3015a95c6a6db45e37250912c4c86697ab]
cip/4.4-st: [1ced0a3015a95c6a6db45e37250912c4c86697ab]
mainline: [bee90911e0138c76ee67458ac0d58b38a3190f65]
stable/4.19: [0aaec9c5f60754b56f84460ea439b8c5e91f4caa]
stable/4.4: [1ced0a3015a95c6a6db45e37250912c4c86697ab]
stable/5.10: [7cf6466e00a77b0a914b7b2c28a1fc7947d55e59]
stable/5.15: [aefcc25f3a0cd28a87d11d41d30419a12cd26a34]
stable/5.4: [79dcbd8176152b860028b62f81a635d987365752]

CVE-2021-47105: ice: xsk: return xsk buffers back to pool when cleaning the ring

Announce: https://lore.kernel.org/linux-cve-announce/2024030444-CVE-2021-47105-fa23@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 2d4238f ("ice: Add support for AF_XDP") in v5.5-rc1.
Tnis commit is not backported to older stable kernels.
Fixed in v5.16-rc7.

Fixed status
mainline: [afe8a3ba85ec2a6b6849367e25c06a2f8e0ddd05]
stable/5.15: [ad6d20da2cfbe14b7b1200d15f39e65988b0b9e8]

CVE-2021-47106: netfilter: nf_tables: fix use-after-free in
nft_set_catchall_destroy()

Announce: https://lore.kernel.org/linux-cve-announce/2024030445-CVE-2021-47106-fdff@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit aaa3104 ("netfilter: nftables: add catch-all set
element support") in v5.13-rc1.
Tnis commit is not backported to older stable kernels.
Fixed in v5.16-rc7.

Fixed status
mainline: [0f7d9b31ce7abdbb29bf018131ac920c9f698518]
stable/5.15: [9d558e5f0d6fdd0a568f73dceb0b40c4f5012e5a]

CVE-2021-47107: NFSD: Fix READDIR buffer overflow

Announce: https://lore.kernel.org/linux-cve-announce/2024030445-CVE-2021-47107-7dda@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit f5dcccd ("NFSD: Update the NFSv2 READDIR entry
encoder to use struct xdr_stream") in v5.13-rc1.
Introduced by commit 7f87fc2 ("NFSD: Update NFSv3 READDIR entry
encoders to use struct xdr_stream") in v5.13-rc1.
These commits are not backported to older stable kernels.
Fixed in v5.16-rc7.

Fixed status
mainline: [53b1119a6e5028b125f431a0116ba73510d82a72]
stable/5.15: [eabc0aab98e5218ceecd82069b0d6fdfff5ee885]

CVE-2021-47108: drm/mediatek: hdmi: Perform NULL pointer check for mtk_hdmi_conf

Announce: https://lore.kernel.org/linux-cve-announce/2024030445-CVE-2021-47108-252a@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 41ca9ca ("drm/mediatek: hdmi: Add check for CEA
modes only") in v5.14-rc1.
Introduced by commit c91026a ("drm/mediatek: hdmi: Add optional limit
on maximal HDMI mode clock") in v5.14-rc1.
These commits are not backported to older stable kernels.
Fixed in v5.16-rc7.

Fixed status
mainline: [3b8e19a0aa3933a785be9f1541afd8d398c4ec69]
stable/5.15: [71d07ebc5000b9c1d140e99e7493b0bafa954776]

CVE-2022-48629: crypto: qcom-rng - ensure buffer for generate is
completely filled

Announce: https://lore.kernel.org/linux-cve-announce/2024030513-CVE-2022-48629-8ee0@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit ceec5f5 ("crypto: qcom-rng - Add Qcom prng
driver") in v4.19-rc1.
Linux 4.4 is not affected.
Fixed in v5.17.

Fixed status
mainline: [a680b1832ced3b5fa7c93484248fd221ea0d614b]
stable/4.19: [a8e32bbb96c25b7ab29b1894dcd45e0b3b08fd9d]
stable/5.10: [0f9b7b8df17525e464294c916acc8194ce38446b]
stable/5.15: [ab9337c7cb6f875b6286440b1adfbeeef2b2b2bd]
stable/5.4: [184f7bd08ce56f003530fc19f160d54e75bf5c9d]

CVE-2022-48630: crypto: qcom-rng - fix infinite loop on requests not
multiple of WORD_SZ

Announce: https://lore.kernel.org/linux-cve-announce/2024030516-CVE-2022-48630-ae00@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit a680b18 ("crypto: qcom-rng - ensure buffer for
generate is completely filled") in v5.17.
This commit is backported to 4.19, 5.4, 5.10, and 5.15. Linux 4.4 is
not affected.
Fixed in v5.18.

Fixed status
mainline: [16287397ec5c08aa58db6acf7dbc55470d78087d]
stable/4.19: [71a89789552b7faf3ef27969b9bc783fa0df3550]
stable/5.10: [233a3cc60e7a8fe0be8cf9934ae7b67ba25a866c]
stable/5.15: [8a06f25f5941c145773204f2f7abef95b4ffb8ce]
stable/5.4: [8be06f62b426801dba43ddf8893952a0e62ab6ae]

CVE-2023-52583: ceph: fix deadlock or deadcode of misusing dget()

Announce: https://lore.kernel.org/linux-cve-announce/2024030641-CVE-2023-52583-fd38@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc1.
This commit seems fix commit ca6c8ae0 ("ceph: pass parent inode info
to ceph_encode_dentry_release if we have it") in 4.11-rc1.
Linux 4.4 alyages get parent inode from dentry->d_parent so Linux 4.4
may not be affected.

Fixed status
mainline: [b493ad718b1f0357394d2cdecbf00a44a36fa085]
stable/4.19: [eb55ba8aa7fb7aad54f40fbf4d8dcdfdba0bebf6]
stable/5.10: [e016e358461b89b231626fcf78c5c38e35c44fd3]
stable/5.15: [a9c15d6e8aee074fae66c04d114f20b84274fcca]
stable/5.4: [6ab4fd508fad942f1f1ba940492f2735e078e980]
stable/6.1: [7f2649c94264d00df6b6ac27161e9f4372a3450e]
stable/6.6: [196b87e5c00ce021e164a5de0f0d04f4116a9160]
stable/6.7: [76cb2aa3421fee4fde706dec41b1344bc0a9ad67]

CVE-2023-52584: spmi: mediatek: Fix UAF on device remove

Announce: https://lore.kernel.org/linux-cve-announce/2024030643-CVE-2023-52584-fb9a@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc1.
The mtk_spmi_probe() is introduced by commit b45b3cce ("spmi:
mediatek: Add support for MT6873/8192") in 5.17-rc1.
This commit is not backported to older stable kernels.

Fixed status
mainline: [e821d50ab5b956ed0effa49faaf29912fd4106d9]
stable/6.1: [521f28eedd6b14228c46e3b81e3bf9b90c2818d8]
stable/6.6: [f8dcafcb54632536684336161da8bdd52120f95e]
stable/6.7: [9a3881b1f07db1bb55cb0108e6f05cfd027eaf2e]

CVE-2023-52585: drm/amdgpu: Fix possible NULL dereference in
amdgpu_ras_query_error_status_helper()

Announce: https://lore.kernel.org/linux-cve-announce/2024030643-CVE-2023-52585-7dbc@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc1.
The affected file drivers/gpu/drm/amd/amdgpu/amdgpu_ras.c is
introduced by commit c030f2e4 ("drm/amdgpu: add amdgpu_ras.c to
support ras (v2)") in 5.2-rc1.
The error query mode handling support is introduced by commit 8cc0f566
("drm/amdgpu: Support multiple error query modes") in 6.7-rc1.
So, prior to Linux 6.7 kernels may not be affected.


Fixed status
mainline: [b8d55a90fd55b767c25687747e2b24abd1ef8680]
stable/6.7: [195a6289282e039024ad30ba66e6f94a4d0fbe49]

CVE-2023-52586: drm/msm/dpu: Add mutex lock in control vblank irq

Announce: https://lore.kernel.org/linux-cve-announce/2024030644-CVE-2023-52586-3ecb@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc1.
The /drivers/gpu/drm/msm/disp directory is not found in Linux 4.4.
Other stable kernels may be affected.

Fixed status
mainline: [45284ff733e4caf6c118aae5131eb7e7cf3eea5a]
stable/6.7: [14f109bf74dd67e1d0469fed859c8e506b0df53f]

CVE-2023-52587: IB/ipoib: Fix mcast list locking

Announce: https://lore.kernel.org/linux-cve-announce/2024030644-CVE-2023-52587-5479@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc1.
Linux 4.4 is affected.

Fixed status
mainline: [4f973e211b3b1c6d36f7c6a19239d258856749f9]
stable/4.19: [4c8922ae8eb8dcc1e4b7d1059d97a8334288d825]
stable/5.10: [ac2630fd3c90ffec34a0bfc4d413668538b0e8f2]
stable/5.15: [ed790bd0903ed3352ebf7f650d910f49b7319b34]
stable/5.4: [615e3adc2042b7be4ad122a043fc9135e6342c90]
stable/6.1: [5108a2dc2db5630fb6cd58b8be80a0c134bc310a]
stable/6.6: [342258fb46d66c1b4c7e2c3717ac01e10c03cf18]
stable/6.7: [7c7bd4d561e9dc6f5b7df9e184974915f6701a89]

CVE-2023-52588: f2fs: fix to tag gcing flag on page during block migration

Announce: https://lore.kernel.org/linux-cve-announce/2024030644-CVE-2023-52588-619a@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc1.
The affected file /fs/f2fs/compress.c doesn't exist in Linux 4.4, 4.19, and 5.4.
The /fs/f2fs/file.c is found in all stable kernels. Linux 4.4 doesn't
have __clone_blkaddrs() and redirty_blocks().
Linux 4.19, 5.4, and 5.10 doesn't have redirty_blocks().

Fixed status
mainline: [4961acdd65c956e97c1a000c82d91a8c1cdbe44b]
stable/5.15: [7ea0f29d9fd84905051be020c0df7d557e286136]
stable/6.1: [7c972c89457511007dfc933814c06786905e515c]
stable/6.6: [417b8a91f4e8831cadaf85c3f15c6991c1f54dde]
stable/6.7: [b8094c0f1aae329b1c60a275a780d6c2c9ff7aa3]

CVE-2023-52589: media: rkisp1: Fix IRQ disable race issue

Announce: https://lore.kernel.org/linux-cve-announce/2024030644-CVE-2023-52589-8f84@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc1.
The /drivers/media/platform/rockchip/rkisp1 directory is not found in
4.4, 4.19, 5.4, and 5.10.

Fixed status
mainline: [870565f063a58576e8a4529f122cac4325c6b395]
stable/6.1: [bf808f58681cab64c81cd814551814fd34e540fe]
stable/6.6: [fab483438342984f2a315fe13c882a80f0f7e545]
stable/6.7: [7bb1a2822aa2c2de4e09bf7c56dd93bd532f1fa7]

CVE-2023-52590: ocfs2: Avoid touching renamed directory if parent does
not change

Announce: https://lore.kernel.org/linux-cve-announce/2024030644-CVE-2023-52590-fca9@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc1.
All stable kernels may be affected.

Fixed status
mainline: [9d618d19b29c2943527e3a43da0a35aea91062fc]
stable/6.7: [de940cede3c41624e2de27f805b490999f419df9]

CVE-2023-52591: reiserfs: Avoid touching renamed directory if parent
does not change

Announce: https://lore.kernel.org/linux-cve-announce/2024030644-CVE-2023-52591-46a0@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc1.
All stable kernels may be affected.

Fixed status
mainline: [49db9b1b86a82448dfaf3fcfefcf678dee56c8ed]
stable/6.6: [17e1361cb91dc1325834da95d2ab532959d2debc]
stable/6.7: [c04c162f82ac403917780eb6d1654694455d4e7c]

CVE-2023-52592: libbpf: Fix NULL pointer dereference in
bpf_object__collect_prog_relos

Announce: https://lore.kernel.org/linux-cve-announce/2024030645-CVE-2023-52592-4693@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc1.
It seems as if this bug is introduced by commit 6245947c1 ("Allow gaps
in BPF program sections to support  overriden weak functions") in
5.13-rc1.

Fixed status
mainline: [fc3a5534e2a8855427403113cbeb54af5837bbe0]
stable/5.15: [90dbf4535668042fac0d7201ce9e2c8c770c578a]
stable/6.1: [12473265f50c1e27b0dfd9735738ac418c4bfcce]
stable/6.6: [5f3e436832e86b826a6450eb8d1aaa51205a758e]
stable/6.7: [ab26541270c722eedf8eefd62797c3ce3d18a91b]

CVE-2023-52593: wifi: wfx: fix possible NULL pointer dereference in
wfx_set_mfp_ap()

Announce: https://lore.kernel.org/linux-cve-announce/2024030645-CVE-2023-52593-14ef@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc1.
The wfx was first introduced by commit a7a91ca5 ("staging: wfx: add
infrastructure for new driver") in 5.5-rc1 to staging directory.
It looks commit 268bcee ("staging: wfx: fix BA when device is AP and
MFP is enabled") in 5.10-rc1. introduced by this bug.

Fixed status
mainline: [fe0a7776d4d19e613bb8dd80fe2d78ae49e8b49d]
stable/6.1: [574dcd3126aa2eed75437137843f254b1190dd03]
stable/6.6: [9ab224744a47363f74ea29c6894c405e3bcf5132]
stable/6.7: [3739121443f5114c6bcf6d841a5124deb006b878]

CVE-2023-52594: wifi: ath9k: Fix potential array-index-out-of-bounds
read in ath9k_htc_txstatus()

Announce: https://lore.kernel.org/linux-cve-announce/2024030645-CVE-2023-52594-9b84@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc1.
Linux 4.4 Linux 4.4 looks to be affected.

Fixed status
mainline: [2adc886244dff60f948497b59affb6c6ebb3c348]
stable/4.19: [f44f073c78112ff921a220d01b86d09f2ace59bc]
stable/5.10: [84770a996ad8d7f121ff2fb5a8d149aad52d64c1]
stable/5.15: [9003fa9a0198ce004b30738766c67eb7373479c9]
stable/5.4: [f11f0fd1ad6c11ae7856d4325fe9d05059767225]
stable/6.1: [25c6f49ef59b7a9b80a3f7ab9e95268a1b01a234]
stable/6.6: [e4f4bac7d3b64eb75f70cd3345712de6f68a215d]
stable/6.7: [be609c7002dd4504b15b069cb7582f4c778548d1]

CVE-2023-52595: wifi: rt2x00: restart beacon queue when hardware reset

Announce: https://lore.kernel.org/linux-cve-announce/2024030645-CVE-2023-52595-d018@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc1.
It looks all stable kernels are affected.

Fixed status
mainline: [a11d965a218f0cd95b13fe44d0bcd8a20ce134a8]
stable/5.10: [69e905beca193125820c201ab3db4fb0e245124e]
stable/5.15: [4cc198580a7b93a36f5beb923f40f7ae27a3716c]
stable/5.4: [e1f113b57ddd18274d7c83618deca25cc880bc48]
stable/6.1: [739b3ccd9486dff04af95f9a890846d088a84957]
stable/6.6: [04cfe4a5da57ab9358cdfadea22bcb37324aaf83]
stable/6.7: [fdb580ed05df8973aa5149cafa598c64bebcd0cb]

CVE-2023-52596: sysctl: Fix out of bounds access for empty sysctl registers

Announce: https://lore.kernel.org/linux-cve-announce/2024030645-CVE-2023-52596-b98e@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc1.
Old stable kernels don't use header for loop iteration.
The ctl_table_size variable was introduced by commit 1e88772 ("sysctl:
Add ctl_table_size to ctl_table_header") in 6.6-rc1.

Fixed status
mainline: [315552310c7de92baea4e570967066569937a843]
stable/6.6: [15893975e9e382f8294ea8d926f08dc2d8d39ede]
stable/6.7: [2ae7081bc10123b187e36a4f3a8e53768de31489]

CVE-2023-52597: KVM: s390: fix setting of fpc register

Announce: https://lore.kernel.org/linux-cve-announce/2024030646-CVE-2023-52597-2ed6@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc1.
s390 is not supported by the CIP.

Fixed status
mainline: [b988b1bb0053c0dcd26187d29ef07566a565cf55]
stable/4.19: [3a04410b0bc7e056e0843ac598825dd359246d18]
stable/5.10: [150a3a3871490e8c454ffbac2e60abeafcecff99]
stable/5.15: [732a3bea7aba5b15026ea42d14953c3425cc7dc2]
stable/5.4: [5e63c9ae8055109d805aacdaf2a4fe2c3b371ba1]
stable/6.1: [0671f42a9c1084db10d68ac347d08dbf6689ecb3]
stable/6.6: [c87d7d910775a025e230fd6359b60627e392460f]
stable/6.7: [2823db0010c400e4b2b12d02aa5d0d3ecb15d7c7]

CVE-2023-52598: s390/ptrace: handle setting of fpc register correctly

Announce: https://lore.kernel.org/linux-cve-announce/2024030646-CVE-2023-52598-d0a2@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc1.
s390 is not supported by the CIP.

Fixed status
mainline: [8b13601d19c541158a6e18b278c00ba69ae37829]
stable/4.19: [6ccf904aac0292e1f6b1a1be6c407c414f7cf713]
stable/5.10: [856caf2730ea18cb39e95833719c02a02447dc0a]
stable/5.15: [28a1f492cb527f64593457a0a0f0d809b3f36c25]
stable/5.4: [6d0822f2cc9b153bf2df49a84599195a2e0d21a8]
stable/6.1: [7a4d6481fbdd661f9e40e95febb95e3dee82bad3]
stable/6.6: [02c6bbfb08bad78dd014e24c7b893723c15ec7a1]
stable/6.7: [bdce67df7f12fb0409fbc604ce7c4254703f56d4]

CVE-2023-52599: jfs: fix array-index-out-of-bounds in diNewExt

Announce: https://lore.kernel.org/linux-cve-announce/2024030646-CVE-2023-52599-b318@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc1.
Linux 4.4 looks to beaffected.

Fixed status
mainline: [49f9637aafa6e63ba686c13cb8549bf5e6920402]
stable/4.19: [f423528488e4f9606cef858eceea210bf1163f41]
stable/5.10: [e2b77d107b33bb31c8b1f5c4cb8f277b23728f1e]
stable/5.15: [6aa30020879042d46df9f747e4f0a486eea6fe98]
stable/5.4: [de6a91aed1e0b1a23e9c11e7d7557f088eeeb017]
stable/6.1: [3537f92cd22c672db97fae6997481e678ad14641]
stable/6.6: [6996d43b14486f4a6655b10edc541ada1b580b4b]
stable/6.7: [5a6660139195f5e2fbbda459eeecb8788f3885fe]

CVE-2023-52600: jfs: fix uaf in jfs_evict_inode

Announce: https://lore.kernel.org/linux-cve-announce/2024030646-CVE-2023-52600-6ffe@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc1.
Linux 4.4 looks to be affected.

Fixed status
mainline: [e0e1958f4c365e380b17ccb35617345b31ef7bf3]
stable/4.19: [81b4249ef37297fb17ba102a524039a05c6c5d35]
stable/5.10: [bc6ef64dbe71136f327d63b2b9071b828af2c2a8]
stable/5.15: [8e44dc3f96e903815dab1d74fff8faafdc6feb61]
stable/5.4: [93df0a2a0b3cde2d7ab3a52ed46ea1d6d4aaba5f]
stable/6.1: [32e8f2d95528d45828c613417cb2827d866cbdce]
stable/6.6: [1696d6d7d4a1b373e96428d0fe1166bd7c3c795e]
stable/6.7: [bacdaa04251382d7efd4f09f9a0686bfcc297e2e]

CVE-2023-52601: jfs: fix array-index-out-of-bounds in dbAdjTree

Announce: https://lore.kernel.org/linux-cve-announce/2024030646-CVE-2023-52601-6c3d@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc1.
Linux 4.4 looks to be affected.

Fixed status
mainline: [74ecdda68242b174920fe7c6133a856fb7d8559b]
stable/4.19: [3d3898b4d72c677d47fe3cb554449f2df5c12555]
stable/5.10: [2037cb9d95f1741885f7daf50e8a028c4ade5317]
stable/5.15: [8393c80cce45f40c1256d72e21ad351b3650c57e]
stable/5.4: [3f8217c323fd6ecd6829a0c3ae7ac3f14eac368e]
stable/6.1: [70780914cb57e2ba711e0ac1b677aaaa75103603]
stable/6.6: [2e16a1389b5a7983b45cb2aa20b0e3f0ee364d6c]
stable/6.7: [fc67a2e18f4c4e3f07e9f9ae463da24530470e73]

CVE-2023-52602: jfs: fix slab-out-of-bounds Read in dtSearch

Announce: https://lore.kernel.org/linux-cve-announce/2024030646-CVE-2023-52602-393a@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc1.
Linux 4.4 looks to be affected.

Fixed status
mainline: [fa5492ee89463a7590a1449358002ff7ef63529f]
stable/4.19: [ce8bc22e948634a5c0a3fa58a179177d0e3f3950]
stable/5.10: [1c40ca3d39d769931b28295b3145c25f1decf5a6]
stable/5.15: [6c6a96c3d74df185ee344977d46944d6f33bb4dd]
stable/5.4: [1b9d6828589d57f94a23fb1c46112cda39d7efdb]
stable/6.1: [cab0c265ba182fd266c2aa3c69d7e40640a7f612]
stable/6.6: [7110650b85dd2f1cee819acd1345a9013a1a62f7]
stable/6.7: [bff9d4078a232c01e42e9377d005fb2f4d31a472]

CVE-2023-52603: UBSAN: array-index-out-of-bounds in dtSplitRoot

Announce: https://lore.kernel.org/linux-cve-announce/2024030647-CVE-2023-52603-e47b@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc1.
Bug is in the fs/jfs/jfs_dtree.c. Linux 4.4 looks to be affected.

Fixed status
mainline: [27e56f59bab5ddafbcfe69ad7a4a6ea1279c1b16]
stable/4.19: [e30b52a2ea3d1e0aaee68096957cf90a2f4ec5af]
stable/5.10: [7aa33854477d9c346f5560a1a1fcb3fe7783e2a8]
stable/5.15: [e4ce01c25ccbea02a09a5291c21749b1fc358e39]
stable/5.4: [fd3486a893778770557649fe28afa5e463d4ed07]
stable/6.1: [e4cbc857d75d4e22a1f75446e7480b1f305d8d60]
stable/6.6: [edff092a59260bf0b0a2eba219cb3da6372c2f9f]
stable/6.7: [6e2902ecc77e9760a9fc447f56d598383e2372d2]

CVE-2023-52604: FS:JFS:UBSAN:array-index-out-of-bounds in dbAdjTree

Announce: https://lore.kernel.org/linux-cve-announce/2024030647-CVE-2023-52604-41d9@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc1.
Bug is in the fs/jfs/jfs_dmap.c. Linux 4.4 looks to be affected.

Fixed status
mainline: [9862ec7ac1cbc6eb5ee4a045b5d5b8edbb2f7e68]
stable/4.19: [e3e95c6850661c77e6dab079d9b5374a618ebb15]
stable/5.10: [de34de6e57bbbc868e4fcf9e98c76b3587cabb0b]
stable/5.15: [6fe8b702125aeee6ce83f20092a2341446704e7b]
stable/5.4: [98f9537fe61b8382b3cc5dd97347531698517c56]
stable/6.1: [42f433785f108893de0dd5260bafb85d7d51db03]
stable/6.6: [6a44065dd604972ec1fbcccbdc4a70d266a89cdd]
stable/6.7: [59342822276f753e49d27ef5eebffbba990572b9]

CVE-2023-52605: ACPI: extlog: fix NULL pointer dereference check

Announce: https://lore.kernel.org/linux-cve-announce/2024030647-CVE-2023-52605-292a@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc1.
Linux 4.4 looks to be affected.

Fixed status
mainline: [72d9b9747e78979510e9aafdd32eb99c7aa30dd1]
stable/4.19: [b7b33627be0626b16ca321b982d6a2261ef7f703]
stable/5.10: [b17a71435e7e153e949df018244a98b4ede04069]
stable/5.15: [5457b0cbaa0238fc56b855c4ef2c0b9cc9c559ab]
stable/5.4: [d2049af7ddbc361702c3e1f09bd6c5e9488454ca]
stable/6.1: [33650372e3ead97c5ab3b84d9ad97737bc5e00c0]
stable/6.6: [f066171de33d71ff0f7c46bd17636a5a26db3fb6]
stable/6.7: [77846571b3ba6a6125a20ad109bb8514ba884cf9]

CVE-2023-52606: powerpc/lib: Validate size for vector operations

Announce: https://lore.kernel.org/linux-cve-announce/2024030647-CVE-2023-52606-fdcc@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc1.
Linux 4.4 seems to be affected.

Fixed status
mainline: [8f9abaa6d7de0a70fc68acaedce290c1f96e2e59]
stable/4.19: [42084a428a139f1a429f597d44621e3a18f3e414]
stable/5.10: [beee482cc4c9a6b1dcffb2e190b4fd8782258678]
stable/5.15: [de4f5ed63b8a199704d8cdcbf810309d7eb4b36b]
stable/5.4: [0580f4403ad33f379eef865c2a6fe94de37febdf]
stable/6.1: [abd26515d4b767ba48241eea77b28ce0872aef3e]
stable/6.6: [28b8ba8eebf26f66d9f2df4ba550b6b3b136082c]
stable/6.7: [848e1d7fd710900397e1d0e7584680c1c04e3afd]

CVE-2023-52607: powerpc/mm: Fix null-pointer dereference in pgtable_cache_add

Announce: https://lore.kernel.org/linux-cve-announce/2024030647-CVE-2023-52607-75d1@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc1.
The fulnerable function pgtable_cache_add() is in the
/arch/powerpc/mm/init_64.c in Linux 4.4. It looks to be affected.

Fixed status
mainline: [f46c8a75263f97bda13c739ba1c90aced0d3b071]
stable/4.19: [21e45a7b08d7cd98d6a53c5fc5111879f2d96611]
stable/5.10: [aa28eecb43cac6e20ef14dfc50b8892c1fbcda5b]
stable/5.15: [ac3ed969a40357b0542d20f096a6d43acdfa6cc7]
stable/5.4: [f6781add1c311c17eff43e14c786004bbacf901e]
stable/6.1: [d482d61025e303a2bef3733a011b6b740215cfa1]
stable/6.6: [145febd85c3bcc5c74d87ef9a598fc7d9122d532]
stable/6.7: [ffd29dc45bc0355393859049f6becddc3ed08f74]

CVE-2024-26623: pds_core: Prevent race issues involving the adminq

Announce: https://lore.kernel.org/linux-cve-announce/2024030648-CVE-2024-26623-ee77@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 01ba61b ("pds_core: Add adminq processing and
commands") in v6.4-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc3.

Fixed status
mainline: [7e82a8745b951b1e794cc780d46f3fbee5e93447]
stable/6.6: [22cd6046eb2148b18990257505834dd45c672a1b]
stable/6.7: [5939feb63ea1f011027576c64b68b681cbad31ca]

CVE-2024-26624: af_unix: fix lockdep positive in sk_diag_dump_icons()

Announce: https://lore.kernel.org/linux-cve-announce/2024030648-CVE-2024-26624-3032@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 2aac7a2 ("unix_diag: Pending connections IDs
NLA") in v3.3-rc1.
Fixed in v6.8-rc3.

Fixed status
mainline: [4d322dce82a1d44f8c83f0f54f95dd1b8dcf46c9]
stable/4.19: [875f31aaa67e306098befa5e798a049075910fa7]
stable/5.10: [f199018dc762dfa501f6d96a424468a0f3c10d9e]
stable/5.15: [c8f6b3b864cb876e9ee21666a391c9ee290682ac]
stable/5.4: [b169ffde733c5adf01788ae091c377f0eca44806]
stable/6.1: [a2104f43876408b164be5fd58f9b6a3a73b77746]
stable/6.6: [5e7f3e0381c002cb2abde42f09ad511991a8ebaf]
stable/6.7: [c2d272a9a1e8f22ba584589219f6fe1886a3595f]

CVE-2024-26625: llc: call sock_orphan() at release time

Announce: https://lore.kernel.org/linux-cve-announce/2024030648-CVE-2024-26625-3549@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 4381548 ("net: sock_def_readable() and friends
RCU conversion") in v2.6.35-rc1.
Fixed in v6.8-rc3.

Fixed status
mainline: [aa2b2eb3934859904c287bf5434647ba72e14c1c]
stable/4.19: [6b950c712a9a05cdda4aea7fcb2848766576c11b]
stable/5.10: [d0b5b1f12429df3cd9751ab8b2f53729b77733b7]
stable/5.15: [dbc1b89981f9c5360277071d33d7f04a43ffda4a]
stable/5.4: [64babb17e8150771c58575d8f93a35c5296b499f]
stable/6.1: [9c333d9891f34cea8af1b229dc754552304c8eee]
stable/6.6: [3151051b787f7cd7e3329ea0016eb9113c248812]
stable/6.7: [8e51f084b5716653f19e291ed5f026791d4b3ed4]

CVE-2024-26626: ipmr: fix kernel panic when forwarding mcast packets

Announce: https://lore.kernel.org/linux-cve-announce/2024030648-CVE-2024-26626-a910@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit bb74036 ("ipmr: support IP_PKTINFO on cache
report IGMP msg") in v6.8-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc3.

Fixed status
mainline: [e622502c310f1069fd9f41cd38210553115f610a]
stable/6.1: [d2f1b7fe74afd66298dbb3c7b39e7b62e4df1724]
stable/6.6: [dcaafdba6c6162bb49f1192850bc3bbc3707738c]
stable/6.7: [2e8c9ae40adda2be1ba41c05fd3cd1e61cce3207]

CVE-2024-26627: scsi: core: Move scsi_host_busy() out of host lock for
waking up EH handler

Announce: https://lore.kernel.org/linux-cve-announce/2024030648-CVE-2024-26627-e3a2@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 6eb045e ("scsi: core: avoid host-wide host_busy
counter for scsi_mq") in v5.5-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc3.

Fixed status
mainline: [4373534a9850627a2695317944898eb1283a2db0]
stable/5.10: [f5944853f7a961fedc1227dc8f60393f8936d37c]
stable/5.15: [d37c1c81419fdef66ebd0747cf76fb8b7d979059]
stable/6.1: [db6338f45971b4285ea368432a84033690eaf53c]
stable/6.6: [65ead8468c21c2676d4d06f50b46beffdea69df1]
stable/6.7: [07e3ca0f17f579491b5f54e9ed05173d6c1d6fcb]

CVE-2024-26628: drm/amdkfd: Fix lock dependency warning

Announce: https://lore.kernel.org/linux-cve-announce/2024030649-CVE-2024-26628-f6ce@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced commit is not determined.Fixed in v6.8-rc1.
Affected functions svm_range_evict_svm_bo_worker() was added by commit
b41896e ("drm/amdkfd: add svm_bo eviction mechanism support "),
svm_range_trigger_migration() was add by commit 0b0e518 ("drm/amdkfd:
HMM migrate ram to vram"),
svm_range_bo_release() was adde by commit e49fe404 ("drm/amdkfd:
validate vram svm range from TTM"). These 3 commits were introduced in
5.14-rc1.

Fixed status
mainline: [47bf0f83fc86df1bf42b385a91aadb910137c5c9]
stable/5.15: [7a70663ba02bd4e19aea8d70c979eb3bd03d839d]
stable/6.1: [8b25d397162b0316ceda40afaa63ee0c4a97d28b]
stable/6.6: [28d2d623d2fbddcca5c24600474e92f16ebb3a05]
stable/6.7: [cb96e492d72d143d57db2d2bc143a1cee8741807]

* Updated CVEs

CVE-2023-52434: smb: client: fix potential OOBs in smb2_parse_contexts()

stable 5.10 and 5.15 were fixed.

Fixed status
mainline: [af1689a9b7701d9907dfc84d2a4b57c4bc907144]
stable/5.10: [13fb0fc4917621f3dfa285a27eaf7151d770b5e5]
stable/5.15: [890bc4fac3c0973a49cac35f634579bebba7fe48]
stable/6.1: [1ae3c59355dc9882e09c020afe8ffbd895ad0f29]
stable/6.6: [17a0f64cc02d4972e21c733d9f21d1c512963afa]

CVE-2024-0565: smb: client: fix OOB in receive_encrypted_standard()

stable 5.10 and 5.15 were fixed.

Fixed status
mainline: [eec04ea119691e65227a97ce53c0da6b9b74b0b7]
stable/5.10: [b03c8099a738a04d2343547ae6a04e5f0f63d3fa]
stable/5.15: [858e73ff25639a0cc1f6f8d2587b62c045867e41]
stable/6.1: [9f528a8e68327117837b5e28b096f52af4c26a05]
stable/6.6: [534733397da26de0303057ce0b93a22bda150365]

CVE-2024-26590: erofs: fix inconsistent per-file compression format

stable 6.1 was fixed.

Fixed status
mainline: [118a8cf504d7dfa519562d000f423ee3ca75d2c4]
stable/6.1: [47467e04816cb297905c0f09bc2d11ef865942d9]
stable/6.6: [823ba1d2106019ddf195287ba53057aee33cf724]
stable/6.7: [eed24b816e50c6cd18cbee0ff0d7218c8fced199]

CVE-2024-26601: ext4: regenerate buddy after block freeing failed if
under fc replay

stable 5.10 and 5.15 were fixed.

Fixed status
mainline: [c9b528c35795b711331ed36dc3dbee90d5812d4e]
stable/5.10: [94ebf71bddbcd4ab1ce43ae32c6cb66396d2d51a]
stable/5.15: [c1317822e2de80e78f137d3a2d99febab1b80326]
stable/6.1: [78327acd4cdc4a1601af718b781eece577b6b7d4]
stable/6.6: [ea42d6cffb0dd27a417f410b9d0011e9859328cb]
stable/6.7: [6b0d48647935e4b8c7b75d1eccb9043fcd4ee581]

CVE-2024-26603: x86/fpu: Stop relying on userspace for info to fault
in xsave buffer

stable 5.15 was fixed.

Fixed status
mainline: [d877550eaf2dc9090d782864c96939397a3c6835]
stable/5.15: [8bd3eee7720c14b59a206bd05b98d7586bccf99a]
stable/6.1: [627339cccdc9166792ecf96bc3c9f711a60ce996]
stable/6.6: [b2479ab426cef7ab79a13005650eff956223ced2]
stable/6.7: [627e28cbb65564e55008315d9e02fbb90478beda]

CVE-2023-2176: Kernel: Slab-out-of-bound read in compare_netdev_and_ip

stable 6.1 was fixed.

Fixed status
mainline: [8d037973d48c026224ab285e6a06985ccac6f7bf]
stable/6.1: [88067197e97af3fcb104dd86030f788ec1b32fdb]

Currently tracking CVEs

CVE-2021-31615: Unencrypted Bluetooth Low Energy baseband links in
Bluetooth Core Specifications 4.0 through 5.2

There is no fix information.

CVE-2020-26556: kernel: malleable commitment Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26557: kernel: predictable Authvalue in Bluetooth Mesh
Provisioning Leads to MITM

No fix information.

CVE-2020-26559: kernel: Authvalue leak in Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26560: kernel: impersonation attack in Bluetooth Mesh Provisioning

No fix information.

Regards,
-- 
Masami Ichikawa
Cybertrust Japan Co., Ltd.

Email :masami.ichikawa@cybertrust.co.jp
          :masami.ichikawa@miraclelinux.com


^ permalink raw reply	[flat|nested] 33+ messages in thread

* [kernel-cve-report] New CVE entries this week
@ 2024-02-29  0:02 Masami Ichikawa
  0 siblings, 0 replies; 33+ messages in thread
From: Masami Ichikawa @ 2024-02-29  0:02 UTC (permalink / raw)
  To: cip-dev

Hi!

It's this week's CVE report.

This week reported 130 new CVEs and 21 updated CVEs.

* New CVEs

CVE-2023-52443: apparmor: avoid crash when parsed profile name is empty

Announce: https://lore.kernel.org/linux-cve-announce/2024022245-CVE-2023-52443-e920@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
apparmor: avoid crash when parsed profile name is empty
When processing a packed profile in unpack_profile() described like
 "profile :ns::samba-dcerpcd /usr/lib*/samba/{,samba/}samba-dcerpcd {...}"
a string ":samba-dcerpcd" is unpacked as a fully-qualified name and then
passed to aa_splitn_fqname().

aa_splitn_fqname() treats ":samba-dcerpcd" as only containing a namespace.
Thus it returns NULL for tmpname, meanwhile tmpns is non-NULL. Later
aa_alloc_profile() crashes as the new profile name is NULL now.

Introduced by commit 04dc715 ("apparmor: audit policy ns specified in
policy load") in 4.11-rc1.
Linux 4.4 is not affected.
Fixed in 6.8-rc1.

Fixed status
mainline: [55a8210c9e7d21ff2644809699765796d4bfb200]
stable/4.19: [9286ee97aa4803d99185768735011d0d65827c9e]
stable/5.10: [5ff00408e5029d3550ee77f62dc15f1e15c47f87]
stable/5.15: [0a12db736edbb4933e4274932aeea594b5876fa4]
stable/5.4: [1d8e62b5569cc1466ceb8a7e4872cf10160a9dcf]
stable/6.1: [9d4fa5fe2b1d56662afd14915a73b4d0783ffa45]
stable/6.6: [5c0392fdafb0a2321311900be83ffa572bef8203]
stable/6.7: [77ab09b92f16c8439a948d1af489196953dc4a0e]

CVE-2023-52444: f2fs: fix to avoid dirent corruption

Announce: https://lore.kernel.org/linux-cve-announce/2024022252-CVE-2023-52444-f7ee@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

A dirent corruption bug was found in the f2fs.

Introduced by commit 7e01e7a ("f2fs: support RENAME_WHITEOUT") in 4.2-rc1.
Fixed in 6.8-rc1.

Fixed status
mainline: [53edb549565f55ccd0bdf43be3d66ce4c2d48b28]
stable/4.19: [02160112e6d45c2610b049df6eb693d7a2e57b46]
stable/5.10: [6f866885e147d33efc497f1095f35b2ee5ec7310]
stable/5.15: [f100ba617d8be6c98a68f3744ef7617082975b77]
stable/5.4: [5624a3c1b1ebc8991318e1cce2aa719542991024]
stable/6.1: [f0145860c20be6bae6785c7a2249577674702ac7]
stable/6.6: [d3c0b49aaa12a61d560528f5d605029ab57f0728]
stable/6.7: [2fb4867f4405aea8c0519d7d188207f232a57862]

CVE-2023-52445: media: pvrusb2: fix use after free on context disconnection

Announce: https://lore.kernel.org/linux-cve-announce/2024022253-CVE-2023-52445-07a6@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
media: pvrusb2: fix use after free on context disconnection Upon
module load,
a kthread is created targeting the pvr2_context_thread_func function,
which may call pvr2_context_destroy and thus call kfree() on the
context
object. However, that might happen before the usb hub_event handler is
able to notify the driver. This patch adds a sanity check before the
invalid read reported by syzbot, within the context disconnection call stack.

Introduced by commit e5be15c ("V4L/DVB (7711): pvrusb2: Fix race on
module unload") in 2.6.26-rc1.
Fixed in 6.8-rc1.

Fixed status
mainline: [ded85b0c0edd8f45fec88783d7555a5b982449c1]
stable/4.19: [ec36c134dd020d28e312c2f1766f85525e747aab]
stable/5.10: [3233d8bf7893550045682192cb227af7fa3defeb]
stable/5.15: [ec3634ebe23fc3c44ebc67c6d25917300bc68c08]
stable/5.4: [47aa8fcd5e8b5563af4042a00f25ba89bef8f33d]
stable/6.1: [30773ea47d41773f9611ffb4ebc9bda9d19a9e7e]
stable/6.6: [2cf0005d315549b8d2b940ff96a66c2a889aa795]
stable/6.7: [437b5f57732bb4cc32cc9f8895d2010ee9ff521c]

CVE-2023-52446: bpf: Fix a race condition between btf_put() and map_free()

Announce: https://lore.kernel.org/linux-cve-announce/2024022254-CVE-2023-52446-2812@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

A race condition bug was found between btf_put() and map_free().

Introduced by commit 958cf2e ("bpf: Introduce bpf_obj_new") in 6.2-rc1.
This commit is not backported to older stable kernels.
Fixed in 6.8-rc1.

Fixed status
mainline: [59e5791f59dd83e8aa72a4e74217eabb6e8cfd90]
stable/6.6: [d048dced8ea5eac6723ae873a40567e6f101ea42]
stable/6.7: [f9ff6ef1c73cd9e1a6bb1ab3e57c5d141a536306]

CVE-2023-52447: bpf: Defer the free of inner map when necessary

Announce: https://lore.kernel.org/linux-cve-announce/2024022255-CVE-2023-52447-e074@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
bpf: Defer the free of inner map when necessary When updating or
deleting an
inner map in map array or map htab, the map may still be accessed by
non-sleepable program or sleepable program. However
bpf_map_fd_put_ptr()
decreases the ref-counter of the inner map directly through
bpf_map_put(), if the ref-counter is the last one (which is true for
most cases), the
inner map will be freed by ops->map_free() in a kworker. But for now,
most .map_free() callbacks don't use synchronize_rcu() or its variants
to
wait for the elapse of a RCU grace period, so after the invocation of
ops->map_free completes, the bpf program which is accessing the inner
map
may incur use-after-free problem. Fix the free of inner map by
invoking bpf_map_free_deferred() after both one RCU grace period and
one tasks
trace RCU grace period if the inner map has been removed from the
outer map before. The deferment is accomplished by using call_rcu() or
call_rcu_tasks_trace() when releasing the last ref-counter of bpf map.
The newly-added rcu_head field in bpf_map shares the same storage
space
with work field to reduce the size of bpf_map.

Introduced by commit 638e4b8 ("bpf: Allows per-cpu maps and map-in-map
in sleepable programs") in 5.12-rc1-dontuse.
This commit is not backported to older stable kernels.
Fixed in 6.8-rc1.

Fixed status
mainline: [876673364161da50eed6b472d746ef88242b2368]
stable/6.1: [62fca83303d608ad4fec3f7428c8685680bb01b0]
stable/6.6: [f91cd728b10c51f6d4a39957ccd56d1e802fc8ee]
stable/6.7: [bfd9b20c4862f41d4590fde11d70a5eeae53dcc5]

CVE-2023-52448: gfs2: Fix kernel NULL pointer dereference in gfs2_rgrp_dump

Announce: https://lore.kernel.org/linux-cve-announce/2024022255-CVE-2023-52448-7bf2@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
gfs2: Fix kernel NULL pointer dereference in gfs2_rgrp_dump Syzkaller
has reported
a NULL pointer dereference when accessing rgd->rd_rgl in
gfs2_rgrp_dump(). This can happen when creating rgd->rd_gl fails in
read_rindex_entry().
Add a NULL pointer check in gfs2_rgrp_dump() to prevent that.

Introduced by commit 72244b6 ("gfs2: improve debug information when
lvb mismatches are found") in 4.20-rc1.
This commit is not backported to older stable kernels.
Fixed in 6.8-rc1.

Fixed status
mainline: [8877243beafa7c6bfc42022cbfdf9e39b25bd4fa]
stable/5.10: [5c28478af371a1c3fdb570ca67f110e1ae60fc37]
stable/5.15: [ee0586d73cbaf0e7058bc640d62a9daf2dfa9178]
stable/5.4: [efc8ef87ab9185a23d5676f2f7d986022d91bcde]
stable/6.1: [d69d7804cf9e2ba171a27e5f98bc266f13d0414a]
stable/6.6: [067a7c48c2c70f05f9460d6f0e8423e234729f05]
stable/6.7: [c323efd620c741168c8e0cc6fc0be04ab57e331a]

CVE-2023-52449: mtd: Fix gluebi NULL pointer dereference caused by ftl notifier

Announce: https://lore.kernel.org/linux-cve-announce/2024022256-CVE-2023-52449-5a7e@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

A NULL pointer dereference caused by ftl notifier in the mtd driver.

Introduced by commit 2ba3d76 ("UBI: make gluebi a separate module") in
2.6.31-rc1.
Fixed in 6.8-rc1.

Fixed status
mainline: [a43bdc376deab5fff1ceb93dca55bcab8dbdc1d6]
stable/4.19: [aeba358bcc8ffddf9b4a9bd0e5ec9eb338d46022]
stable/5.10: [001a3f59d8c914ef8273461d4bf495df384cc5f8]
stable/5.15: [d8ac2537763b54d278b80b2b080e1652523c7d4c]
stable/5.4: [1bf4fe14e97cda621522eb2f28b0a4e87c5b0745]
stable/6.1: [5389407bba1eab1266c6d83e226fb0840cb98dd5]
stable/6.6: [cfd7c9d260dc0a3baaea05a122a19ab91e193c65]
stable/6.7: [b36aaa64d58aaa2f2cbc8275e89bae76a2b6c3dc]

CVE-2023-52450: perf/x86/intel/uncore: Fix NULL pointer dereference
issue in upi_fill_topology()

Announce: https://lore.kernel.org/linux-cve-announce/2024022256-CVE-2023-52450-48ba@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
perf/x86/intel/uncore: Fix NULL pointer dereference issue in
upi_fill_topology()
Get logical socket id instead of physical id in
discover_upi_topology() to avoid out-of-bound access on 'upi =
&type->topology[nid][idx];'
line that leads to NULL pointer dereference in upi_fill_topology().

Introduced by commit f680b6e ("perf/x86/intel/uncore: Enable UPI
topology discovery for Icelake Server") in 6.2-rc1.
This commit is not backported to older stable kernels.
Fixed in 6.8-rc1.

Fixed status
mainline: [1692cf434ba13ee212495b5af795b6a07e986ce4]
stable/6.6: [bf1bf09e6b599758851457f3999779622a48d015]
stable/6.7: [3d6f4a78b104c65e4256c3776c9949f49a1b459e]

CVE-2023-52451: powerpc/pseries/memhp: Fix access beyond end of drmem array

Announce: https://lore.kernel.org/linux-cve-announce/2024022257-CVE-2023-52451-7bdb@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
powerpc/pseries/memhp: Fix access beyond end of drmem array
dlpar_memory_remove_by_index() may access beyond the bounds of the
drmem lmb array when the LMB lookup fails to match an entry with the
given
DRC index. When the search fails, the cursor is left pointing to
&drmem_info->lmbs[drmem_info->n_lmbs], which is one element past the
last valid
entry in the array.

Introduced by commit 51925fb ("powerpc/pseries: Implement memory
hotplug remove in the kernel") in 4.1-rc1.
Fixed in 6.8-rc1.

Fixed status
mainline: [bd68ffce69f6cf8ddd3a3c32549d1d2275e49fc5]
stable/4.19: [bb79613a9a704469ddb8d6c6029d532a5cea384c]
stable/5.10: [b582aa1f66411d4adcc1aa55b8c575683fb4687e]
stable/5.15: [999a27b3ce9a69d54ccd5db000ec3a447bc43e6d]
stable/5.4: [9b5f03500bc5b083c0df696d7dd169d7ef3dd0c7]
stable/6.1: [026fd977dc50ff4a5e09bfb0603557f104d3f3a0]
stable/6.6: [df16afba2378d985359812c865a15c05c70a967e]
stable/6.7: [708a4b59baad96c4718dc0bd3a3427d3ab22fedc]

CVE-2023-52452: bpf: Fix accesses to uninit stack slots

Announce: https://lore.kernel.org/linux-cve-announce/2024022258-CVE-2023-52452-7904@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Privileged programs are supposed to be able to read uninitialized
stack memory (ever since 6715df8d5) but, before this patch, these
accesses
were permitted inconsistently. In particular, accesses were permitted
above state->allocated_stack, but not below it. In other words, if the
stack was already "large enough", the access was permitted, but
otherwise the access was rejected instead of being allowed to "grow
the stack".
This undesired rejection was happening in two places:
- in check_stack_slot_within_bounds()
- in check_stack_range_initialized()

Introduced by commit 01f810a ("bpf: Allow variable-offset stack
access") in 5.12-rc1-dontuse.
This patch is backported to 5.10.
Fixed in 6.8-rc1.

Fixed status
mainline: [6b4a64bafd107e521c01eec3453ce94a3fb38529]
stable/6.6: [0954982db8283016bf38e9db2da5adf47a102e19]
stable/6.7: [fbcf372c8eda2290470268e0afb5ab5d5f5d5fde]

CVE-2024-26586: mlxsw: spectrum_acl_tcam: Fix stack corruption

Announce: https://lore.kernel.org/linux-cve-announce/2024022253-CVE-2024-26586-6632@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

When tc filters are first added to a net device, the corresponding
local port gets bound to an ACL group in the device. The group
contains a list
of ACLs. In turn, each ACL points to a different TCAM region where the
filters are stored. During forwarding, the ACLs are sequentially
evaluated until a match is found.
One reason to place filters in different regions is when they are
added with decreasing priorities and in an alternating order so that
two
consecutive filters can never fit in the same region because of their key usage.
In Spectrum-2 and newer ASICs the firmware started to report that the
maximum number of ACLs in a group is more than 16, but the layout of
the
register that configures ACL groups (PAGT) was not updated to account
for that. It is therefore possible to hit stack corruption in the
rare case where more than 16 ACLs in a group are required.

Introduced by commit c3ab435 ("mlxsw: spectrum: Extend to support
Spectrum-2 ASIC") in 4.19-rc1.
This commit is not backported to 4.4.
Fixed in 6.8-rc1.

Fixed status
mainline: [483ae90d8f976f8339cf81066312e1329f2d3706]
stable/5.10: [56750ea5d15426b5f307554e7699e8b5f76c3182]
stable/5.15: [348112522a35527c5bcba933b9fefb40a4f44f15]
stable/6.1: [6fd24675188d354b1cad47462969afa2ab09d819]
stable/6.6: [2f5e1565740490706332c06f36211d4ce0f88e62]
stable/6.7: [a361c2c1da5dbb13ca67601cf961ab3ad68af383]

CVE-2024-26587: net: netdevsim: don't try to destroy PHC on VFs

Announce: https://lore.kernel.org/linux-cve-announce/2024022255-CVE-2024-26587-db74@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

A NULL pointer dereference bug was found in the netdevsim.

Introduced by commit b63e78f ("net: netdevsim: use mock PHC driver") in 6.6-rc1.
This commit is not backported to older stable kernels.
Fixed in 6.8-rc1.

Fixed status
mainline: [ea937f77208323d35ffe2f8d8fc81b00118bfcda]
stable/6.6: [08aca65997fb6f233066883b1f1e653bcb1f26ca]
stable/6.7: [c5068e442eed063d2f1658e6b6d3c1c6fcf1e588]

CVE-2024-26588: LoongArch: BPF: Prevent out-of-bounds memory access

Announce: https://lore.kernel.org/linux-cve-announce/2024022256-CVE-2024-26588-d6d5@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

An OOB access bug was found in BPF on LoongArch architecture when
building instructions in build_insn().

Introduced by commit bbfddb9 ("LoongArch: BPF: Avoid declare variables
in switch-case") in 6.1-rc3.
This commit is not backported to older stable kernels.
Fixed in 6.8-rc1.

Fixed status
mainline: [36a87385e31c9343af9a4756598e704741250a67]
stable/6.1: [4631c2dd69d928bca396f9f58baeddf85e14ced5]
stable/6.6: [9aeb09f4d85a87bac46c010d75a2ea299d462f28]
stable/6.7: [7924ade13a49c0067da6ea13e398102979c0654a]

CVE-2024-26589: bpf: Reject variable offset alu on PTR_TO_FLOW_KEYS

Announce: https://lore.kernel.org/linux-cve-announce/2024022257-CVE-2024-26589-0ee1@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

For PTR_TO_FLOW_KEYS, check_flow_keys_access() only uses fixed off for
validation. However, variable offset ptr alu is not prohibited
for this ptr kind. So the variable offset is not checked.

Introduced by commit d58e468 ("flow_dissector: implements flow
dissector BPF hook") in 4.20-rc1.
This commit is not backported to older stable kernels.
Fixed in 6.8-rc1.

Fixed status
mainline: [22c7fa171a02d310e3a3f6ed46a698ca8a0060ed]
stable/5.15: [29ffa63f21bcdcef3e36b03cccf9d0cd031f6ab0]
stable/6.1: [4108b86e324da42f7ed425bd71632fd844300dc8]
stable/6.6: [e8d3872b617c21100c5ee4f64e513997a68c2e3d]
stable/6.7: [1b500d5d6cecf98dd6ca88bc9e7ae1783c83e6d3]

CVE-2024-26590: erofs: fix inconsistent per-file compression format

Announce: https://lore.kernel.org/linux-cve-announce/2024022259-CVE-2024-26590-85a4@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

When invalid algorithm type for specific inodes is used in a crafted
image, that causes a NULL pointer dereference bug in the erofs.

Introduced by commit 622cead ("erofs: lzma compression support") in 5.16-rc1.
This commit is not backported to older stable kernels.
Fixed in 6.8-rc1.

Fixed status
mainline: [118a8cf504d7dfa519562d000f423ee3ca75d2c4]
stable/6.6: [823ba1d2106019ddf195287ba53057aee33cf724]
stable/6.7: [eed24b816e50c6cd18cbee0ff0d7218c8fced199]

CVE-2024-26591: bpf: Fix re-attachment branch in bpf_tracing_prog_attach

Announce: https://lore.kernel.org/linux-cve-announce/2024022258-CVE-2024-26591-8b42@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

The following case can cause a crash due to missing attach_btf:

1) load rawtp program
2) load fentry program with rawtp as target_fd
3) create tracing link for fentry program with target_fd = 0
4) repeat 3

Introduced by commit f3a9507 ("bpf: Allow trampoline re-attach for
tracing and lsm programs") in 5.13-rc1.
This commit is not backported to older stable kernels.
Fixed in 6.8-rc1.

Fixed status
mainline: [715d82ba636cb3629a6e18a33bb9dbe53f9936ee]
stable/5.15: [a7b98aa10f895e2569403896f2d19b73b6c95653]
stable/6.1: [6cc9c0af0aa06f781fa515a1734b1a4239dfd2c0]
stable/6.6: [8c8bcd45e9b10eef12321f08d2e5be33d615509c]
stable/6.7: [50ae82f080cf87e84828f066c31723b781d68f5b]

CVE-2024-26592: ksmbd: fix UAF issue in ksmbd_tcp_new_connection()

Announce: https://lore.kernel.org/linux-cve-announce/2024022259-CVE-2024-26592-58f7@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
ksmbd: fix UAF issue in ksmbd_tcp_new_connection().
The race is between the handling of a new TCP connection and its
disconnection. It leads to UAF on `struct tcp_transport` in
ksmbd_tcp_new_connection() function.

The ksmbd was introduced in 5.15 so prior to the 5.15 kernels aren't affected.
Fixed in 6.8-rc1.

Fixed status
mainline: [38d20c62903d669693a1869aa68c4dd5674e2544]
stable/5.15: [999daf367b924fdf14e9d83e034ee0f86bc17ec6]
stable/6.1: [380965e48e9c32ee4263c023e1d830ea7e462ed1]
stable/6.6: [24290ba94cd0136e417283b0dbf8fcdabcf62111]
stable/6.7: [69d54650b751532d1e1613a4fb433e591aeef126]

CVE-2024-26593: i2c: i801: Fix block process call transactions

Announce: https://lore.kernel.org/linux-cve-announce/2024022315-CVE-2024-26593-9d89@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

According to the Intel datasheets, software must reset the block
buffer index twice for block process call transactions: once before
writing the outgoing data to the buffer, and once again before reading
the incoming data from the buffer.
The driver is currently missing the second reset, causing the wrong
portion of the block buffer to be read.

Introduced by commit 315cd67 ("i2c: i801: Add Block Write-Block Read
Process Call support") in 5.3-rc1.
This commit is not backported to older stable kernels.
Fixed in 6.8-rc5.

Fixed status
mainline: [c1c9d0f6f7f1dbf29db996bd8e166242843a5f21]
stable/5.10: [7a14b8a477b88607d157c24aeb23e7389ec3319f]
stable/5.15: [1f8d0691c50581ba6043f009ec9e8b9f78f09d5a]
stable/5.4: [d074d5ff5ae77b18300e5079c6bda6342a4d44b7]
stable/6.1: [491528935c9c48bf341d8b40eabc6c4fc5df6f2c]
stable/6.6: [6be99c51829b24c914cef5bff6164877178e84d9]
stable/6.7: [609c7c1cc976e740d0fed4dbeec688b3ecb5dce2]

CVE-2023-52453: hisi_acc_vfio_pci: Update migration data pointer
correctly on saving/resume

Announce: https://lore.kernel.org/linux-cve-announce/2024022325-CVE-2023-52453-9f24@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
hisi_acc_vfio_pci: Update migration data pointer correctly on
saving/resume
When the optional PRE_COPY support was added to speed up the device
compatibility check, it failed to update the saving/resuming data
pointers
based on the fd offset. This results in migration data corruption

Introduced by commit d9a871e ("hisi_acc_vfio_pci: Introduce support
for PRE_COPY state transitions") in 6.2-rc1.
This commit is not backported to older stable kernels.
Fixed in 6.8-rc1.

Fixed status
mainline: [be12ad45e15b5ee0e2526a50266ba1d295d26a88]
stable/6.6: [45f80b2f230df10600e6fa1b83b28bf1c334185e]
stable/6.7: [6bda81e24a35a856f58e6a5786de579b07371603]

CVE-2023-52454: nvmet-tcp: Fix a kernel panic when host sends an
invalid H2C PDU length

Announce: https://lore.kernel.org/linux-cve-announce/2024022330-CVE-2023-52454-5cf0@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

If the host sends an H2CData command with an invalid DATAL, the kernel
may crash in nvmet_tcp_build_pdu_iovec().

Introduced by commit 872d26a ("nvmet-tcp: add NVMe over TCP target
driver") in 5.0-rc1.
This commit is not backported to older stable kernels.
Fixed in 6.8-rc1.

Fixed status
mainline: [efa56305908ba20de2104f1b8508c6a7401833be]
stable/5.10: [f775f2621c2ac5cc3a0b3a64665dad4fb146e510]
stable/5.15: [4cb3cf7177ae3666be7fb27d4ad4d72a295fb02d]
stable/5.4: [ee5e7632e981673f42a50ade25e71e612e543d9d]
stable/6.1: [2871aa407007f6f531fae181ad252486e022df42]
stable/6.6: [24e05760186dc070d3db190ca61efdbce23afc88]
stable/6.7: [70154e8d015c9b4fb56c1a2ef1fc8b83d45c7f68]

CVE-2023-52455: iommu: Don't reserve 0-length IOVA region

Announce: https://lore.kernel.org/linux-cve-announce/2024022331-CVE-2023-52455-a28f@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
iommu: Don't reserve 0-length IOVA region When the bootloader/firmware
doesn't setup the framebuffers, their address and size are 0 in
"iommu-addresses" property. If IOVA region is reserved with 0 length,
then
it ends up corrupting the IOVA rbtree with an entry which has pfn_hi <
pfn_lo. If we intend to use display driver in kernel without
framebuffer
then it's causing the display IOMMU mappings to fail as entire valid
IOVA space is reserved when address and length are passed as 0.
An ideal solution would be firmware removing the "iommu-addresses"
property and corresponding "memory-region" if display is not present.
But the kernel should be able to handle this by checking for size of
IOVA region and skipping the IOVA reservation if size is 0. Also, add
a
warning if firmware is requesting 0-length IOVA region reservation.

Introduced by commit a5bf3cf ("iommu: Implement
of_iommu_get_resv_regions()") in 6.3-rc1.
This commit is not backported to older stable kernels.
Fixed in 6.8-rc1.

Fixed status
mainline: [bb57f6705960bebeb832142ce9abf43220c3eab1]
stable/6.6: [98b8a550da83cc392a14298c4b3eaaf0332ae6ad]
stable/6.7: [5e23e283910c9f30248732ae0770bcb0c9438abf]

CVE-2023-52456: serial: imx: fix tx statemachine deadlock

Announce: https://lore.kernel.org/linux-cve-announce/2024022331-CVE-2023-52456-f9dd@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
serial: imx: fix tx statemachine deadlock When using the serial port
as RS485 port,
the tx statemachine is used to control the RTS pin to drive the RS485
transceiver TX_EN pin. When the TTY port is closed in the middle of a
transmission
 (for instance during userland application crash), imx_uart_shutdown
disables the interface and disables the Transmission Complete
interrupt. afer that,
 imx_uart_stop_tx bails on an incomplete transmission, to be
retriggered by the TC interrupt. This interrupt is disabled and
therefore the tx statemachine
 never transitions out of SEND. The statemachine is in deadlock now,
and the TX_EN remains low, making the interface useless.
imx_uart_stop_tx now checks
 for incomplete transmission AND whether TC interrupts are enabled
before bailing to be retriggered. This makes sure the state machine
handling is reached,
 and is properly set to WAIT_AFTER_SEND.

Introduced by commit cb1a609 ("serial: imx: implement rts delaying for
rs485") in 5.9-rc1.
This commit is not backported to older stable kernels.
Fixed in 6.8-rc1.

Fixed status
mainline: [78d60dae9a0c9f09aa3d6477c94047df2fe6f7b0]
stable/5.10: [6e04a9d30509fb53ba6df5d655ed61d607a7cfda]
stable/5.15: [ff168d4fdb0e1ba35fb413a749b3d6cce918ec19]
stable/6.1: [63ee7be01a3f7d28b1ea8b8d7944f12bb7b0ed06]
stable/6.6: [763cd68746317b5d746dc2649a3295c1efb41181]
stable/6.7: [9a662d06c22ddfa371958c2071dc350436be802b]

CVE-2023-52457: serial: 8250: omap: Don't skip resource freeing if
pm_runtime_resume_and_get() failed

Announce: https://lore.kernel.org/linux-cve-announce/2024022332-CVE-2023-52457-c7b9@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
serial: 8250: omap: Don't skip resource freeing if
pm_runtime_resume_and_get()
failed Returning an error code from .remove() makes the driver core
emit the little helpful error message: remove callback returned a
non-zero value.
This will be ignored. and then remove the device anyhow. So all
resources that were not freed are leaked in this case. Skipping
serial8250_unregister_port() has the potential to keep enough of the
UART around to trigger a use-after-free. So replace the error return
(and with it the little helpful error message) by a more useful error
message and continue to cleanup.

Introduced by commit e3f0c63 ("serial: 8250: omap: Fix unpaired
pm_runtime_put_sync() in omap8250_remove()") in 6.1-rc6.
This commit is not backported to 4.x kernels.
Fixed in 6.8-rc1.

mainline: [ad90d0358bd3b4554f243a425168fc7cebe7d04e]
stable/5.10: [bc57f3ef8a9eb0180606696f586a6dcfaa175ed0]
stable/5.15: [828cd829483f0cda920710997aed79130b0af690]
stable/5.4: [b502fb43f7fb55aaf07f6092ab44657595214b93]
stable/6.1: [d74173bda29aba58f822175d983d07c8ed335494]
stable/6.6: [887a558d0298d36297daea039954c39940228d9b]
stable/6.7: [95e4e0031effad9837af557ecbfd4294a4d8aeee]

CVE-2023-52458: block: add check that partition length needs to be
aligned with block size

Announce: https://lore.kernel.org/linux-cve-announce/2024022332-CVE-2023-52458-d1cd@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
block: add check that partition length needs to be aligned with block
size Before
calling add partition or resize partition, there is no check on
whether the length is aligned with the logical block size. If the
logical block size of
the disk is larger than 512 bytes, then the partition size maybe not
the multiple of the logical block size, and when the last sector is
read,
bio_truncate() will adjust the bio size, resulting in an IO error if
the size of the read command is smaller than the logical block size.If
integrity
data is supported, this will also result in a null pointer dereference
when calling bio_integrity_free.

Fixed in 6.8-rc1.

Fixed status
mainline: [6f64f866aa1ae6975c95d805ed51d7e9433a0016]
stable/5.15: [5010c27120962c85d2f421d2cf211791c9603503]
stable/6.1: [ef31cc87794731ffcb578a195a2c47d744e25fb8]
stable/6.6: [cb16cc1abda18a9514106d2ac8c8d7abc0be5ed8]
stable/6.7: [bcdc288e7bc008daf38ef0401b53e4a8bb61bbe5]

CVE-2023-52459: media: v4l: async: Fix duplicated list deletion

Announce: https://lore.kernel.org/linux-cve-announce/2024022333-CVE-2023-52459-f653@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
media: v4l: async: Fix duplicated list deletion The list deletion call
dropped here
is already called from the helper function in the line before. Having
a second list_del() call results in either a warning (with
CONFIG_DEBUG_LIST=y):
list_del corruption, c46c8198->next is LIST_POISON1 (00000100) If
CONFIG_DEBUG_LIST is disabled the operation results in a kernel error
due to NULL
pointer dereference.

Introduced by commit 28a1295 ("media: v4l: async: Allow multiple
connections between entities") in 6.6-rc1.
This commit is not backported to older stable kernels.
Fixed in 6.8-rc1.

Fixed status
mainline: [3de6ee94aae701fa949cd3b5df6b6a440ddfb8f2]
stable/6.6: [b7062628caeaec90e8f691ebab2d70f31b7b6b91]
stable/6.7: [49d82811428469566667f22749610b8c132cdb3e]

CVE-2023-52460: drm/amd/display: Fix NULL pointer dereference at hibernate

Announce: https://lore.kernel.org/linux-cve-announce/2024022333-CVE-2023-52460-a52b@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Fix NULL pointer dereference at hibernate During
hibernate sequence the source context
might not have a clk_mgr. So don't use it to look for DML2 support.

Introduced by commit 7966f31 ("drm/amd/display: Introduce DML2") in 6.7-rc1.
This commit is not backported to older stable kernels.
Fixed in 6.8-rc1.

Fixed status
mainline: [b719a9c15d52d4f56bdea8241a5d90fd9197ce99]
stable/6.7: [6b80326efff093d037e0971831dca6ebddba9b45]

CVE-2023-52461: drm/sched: Fix bounds limiting when given a malformed entity

Announce: https://lore.kernel.org/linux-cve-announce/2024022334-CVE-2023-52461-a619@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
drm/sched: Fix bounds limiting when given a malformed entity If we're
given a malformed
entity in drm_sched_entity_init()--shouldn't happen, but we
verify--with out-of-bounds priority value, we set it to an allowed
value. Fix the expression
which sets this limit.

Introduced by commit 56e4496 ("drm/sched: Convert the GPU scheduler to
variable number of run-queues") in 6.7-rc1.
This commit is not backported to older stable kernels.
Fixed in 6.8-rc1.

Fixed status
mainline: [2bbe6ab2be53858507f11f99f856846d04765ae3]
stable/6.7: [1470d173925d697b497656b93f7c5bddae2e64b2]

CVE-2023-52462: bpf: fix check for attempt to corrupt spilled pointer

Announce: https://lore.kernel.org/linux-cve-announce/2024022335-CVE-2023-52462-b663@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
bpf: fix check for attempt to corrupt spilled pointer When register is
spilled
onto a stack as a 1/2/4-byte register, we set slot_type[BPF_REG_SIZE -
1] (plus potentially few more below it, depending on actual spill
size).
So to check if some stack slot has spilled register we need to consult
slot_type[7], not slot_type[0]. To avoid the need to remember and
double-check
this in the future, just use is_spilled_reg() helper.

Introduced by commit 27113c5 ("bpf: Check the other end of slot_type
for STACK_SPILL") in 5.16-rc1.
This commit is not backported to 5.4 and 4.x kernels.
Fixed in 6.8-rc1.

Fixed status
mainline: [ab125ed3ec1c10ccc36bc98c7a4256ad114a3dae]
stable/5.10: [2757f17972d87773b3677777f5682510f13c66ef]
stable/5.15: [67e6707f07354ed1acb4e65552e97c60cf9d69cf]
stable/6.1: [fc3e3c50a0a4cac1463967c110686189e4a59104]
stable/6.6: [8dc15b0670594543c356567a1a45b0182ec63174]
stable/6.7: [40617d45ea05535105e202a8a819e388a2b1f036]

CVE-2023-52463: efivarfs: force RO when remounting if SetVariable is
not supported

Announce: https://lore.kernel.org/linux-cve-announce/2024022335-CVE-2023-52463-6195@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
efivarfs: force RO when remounting if SetVariable is not supported If
SetVariable
at runtime is not supported by the firmware we never assign a callback
for that function. At the same time mount the efivarfs as RO so no one
can
call that. However, we never check the permission flags when someone
remounts the filesystem as RW. As a result this leads to a crash.

Introduced by commit f88814c ("efi/efivars: Expose RT service
availability via efivars abstraction") in 5.8-rc7.
This commit is not backported to older stable kernels.
Fixed in 6.8-rc1.

Fixed status
mainline: [0e8d2444168dd519fea501599d150e62718ed2fe]
stable/5.10: [94c742324ed7e42c5bd6a9ed22e4ec6d764db4d8]
stable/5.15: [2aa141f8bc580f8f9811dfe4e0e6009812b73826]
stable/6.1: [d4a9aa7db574a0da64307729cc031fb68597aa8b]
stable/6.6: [0049fe7e4a85849bdd778cdb72e51a791ff3d737]
stable/6.7: [d4a714873db0866cc471521114eeac4a5072d548]

CVE-2023-52464: EDAC/thunderx: Fix possible out-of-bounds string access

Announce: https://lore.kernel.org/linux-cve-announce/2024022336-CVE-2023-52464-b17c@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Enabling -Wstringop-overflow globally exposes a warning for a common
bug in the usage of strncat().
Apparently the author of this driver expected strncat() to behave the
way that strlcat() does, which uses the size of the destination buffer
as its third argument rather than the length of the source buffer. The
result is that there is no check on the size of the allocated buffer.

Introduced by commit 4100339 ("EDAC, thunderx: Add Cavium ThunderX
EDAC driver") in 4.12-rc1.
This commit is not backported to 4.4.
Fixed in 6.8-rc1.

Fixed status
mainline: [475c58e1a471e9b873e3e39958c64a2d278275c8]
stable/4.19: [71c17ee02538802ceafc830f0736aa35b564e601]
stable/5.10: [6aa7865ba7ff7f0ede0035180fb3b9400ceb405a]
stable/5.15: [700cf4bead80fac994dcc43ae1ca5d86d8959b21]
stable/5.4: [5da3b6e7196f0b4f3728e4e25eb20233a9ddfaf6]
stable/6.1: [9dbac9fdae6e3b411fc4c3fca3bf48f70609c398]
stable/6.6: [e1c86511241588efffaa49556196f09a498d5057]
stable/6.7: [426fae93c01dffa379225eb2bd4d3cdc42c6eec5]

CVE-2024-26594: ksmbd: validate mech token in session setup

Announce: https://lore.kernel.org/linux-cve-announce/2024022325-CVE-2024-26594-1cbc@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

If a client send invalid mech token in a session setup request, ksmbd
validates and makes the error if it is invalid.

The ksmbd was introduced in 5.15.
Fixed in 6.8-rc1.

Fixed status
mainline: [92e470163d96df8db6c4fa0f484e4a229edb903d]
stable/5.15: [dd1de9268745f0eac83a430db7afc32cbd62e84b]
stable/6.1: [6eb8015492bcc84e40646390e50a862b2c0529c9]
stable/6.6: [a2b21ef1ea4cf632d19b3a7cc4d4245b8e63202a]
stable/6.7: [5e6dfec95833edc54c48605a98365a7325e5541e]

CVE-2024-26595: mlxsw: spectrum_acl_tcam: Fix NULL pointer dereference
in error path

Announce: https://lore.kernel.org/linux-cve-announce/2024022336-CVE-2024-26595-9a8d@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

When calling mlxsw_sp_acl_tcam_region_destroy() from an error path
after failing to attach the region to an ACL group, we hit a NULL
pointer
dereference upon 'region->group->tcam'

Introduced by commit 22a6776 ("mlxsw: spectrum: Introduce ACL core
with simple TCAM implementation") in 4.11-rc1.
This commit is not backported to 4.4.
Fixed in 6.8-rc1.

Fixed status
mainline: [efeb7dfea8ee10cdec11b6b6ba4e405edbe75809]
stable/6.6: [817840d125a370626895df269c50c923b79b0a39]
stable/6.7: [d0a1efe417c97a1e9b914056ee6b86f1ef75fe1f]

CVE-2024-26596: net: dsa: fix netdev_priv() dereference before check
on non-DSA netdevice events

Announce: https://lore.kernel.org/linux-cve-announce/2024022336-CVE-2024-26595-9a8d@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

An out-of-bound access bug was found in the net/dsa subsystem.

Introduced by commit 4c3f80d ("net: dsa: walk through all changeupper
notifier functions") in 6.1-rc1.
This commit is not backported to older stable kernels.
Fixed in 6.8-rc1.

Fixed status
mainline: [844f104790bd69c2e4dbb9ee3eba46fde1fcea7b]
stable/6.7: [dbd909c20c11f0d29c0054d41e0d1f668a60e8c8]

CVE-2024-26597: net: qualcomm: rmnet: fix global oob in rmnet_policy

Announce: https://lore.kernel.org/linux-cve-announce/2024022337-CVE-2024-26597-be75@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 14452ca ("net: qualcomm: rmnet: Export mux_id and
flags to netlink") in 4.17-rc1.
This commit is not backported to older stable kernels.
Fixed in 6.8-rc1.

Fixed status
mainline: [b33fb5b801c6db408b774a68e7c8722796b59ecc]
stable/4.19: [093dab655808207f7a9f54cf156240aeafc70590]
stable/5.10: [2295c22348faf795e1ccdf618f6eb7afdb2f7447]
stable/5.15: [3b5254862258b595662a0ccca6e9eeb88d6e7468]
stable/5.4: [02467ab8b404d80429107588e0f3425cf5fcd2e5]
stable/6.1: [ee1dc3bf86f2df777038506b139371a9add02534]
stable/6.6: [c4734535034672f59f2652e1e0058c490da62a5c]
stable/6.7: [17d06a5c44d8fd2e8e61bac295b09153496f87e1]

CVE-2024-26598: KVM: arm64: vgic-its: Avoid potential UAF in LPI
translation cache

Announce: https://lore.kernel.org/linux-cve-announce/2024022338-CVE-2024-26598-24f4@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
KVM: arm64: vgic-its: Avoid potential UAF in LPI translation cache
There
is a potential UAF scenario in the case of an LPI translation cache
hit racing with an operation that invalidates the cache, such as a
DISCARD
ITS command. The root of the problem is that vgic_its_check_cache()
does not elevate the refcount on the vgic_irq before dropping the lock
that serializes refcount changes. Have vgic_its_check_cache() raise
the refcount on the returned vgic_irq and add the corresponding
decrement
after queueing the interrupt.

Fixed in 6.8-rc1.

Fixed status
mainline: [ad362fe07fecf0aba839ff2cc59a3617bd42c33f]
stable/5.10: [ba7be666740847d967822bed15500656b26bc703]
stable/5.15: [12c2759ab1343c124ed46ba48f27bd1ef5d2dff4]
stable/5.4: [d04acadb6490aa3314f9c9e087691e55de153b88]
stable/6.1: [dba788e25f05209adf2b0175eb1691dc89fb1ba6]
stable/6.6: [65b201bf3e9af1b0254243a5881390eda56f72d1]
stable/6.7: [dd3956a1b3dd11f46488c928cb890d6937d1ca80]

CVE-2024-26599: pwm: Fix out-of-bounds access in of_pwm_single_xlate()

Announce: https://lore.kernel.org/linux-cve-announce/2024022338-CVE-2024-26599-cd65@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
pwm: Fix out-of-bounds access in of_pwm_single_xlate()
With args->args_count == 2 args->args[2] is not defined. Actually the
flags are contained in args->args[1].

Introduced by commit 3ab7b6a ("pwm: Introduce single-PWM of_xlate
function") in 5.17-rc1.
This commit is not backported to older stable kernels.
Fixed in 6.8-rc1.

Fixed status
mainline: [a297d07b9a1e4fb8cda25a4a2363a507d294b7c9]
stable/6.1: [7b85554c7c2aee91171e038e4d5442ffa130b282]
stable/6.6: [e5f2b4b62977fb6c2efcbc5779e0c9dce18215f7]
stable/6.7: [bae45b7ebb31984b63b13c3519fd724b3ce92123]

CVE-2024-26600: phy: ti: phy-omap-usb2: Fix NULL pointer dereference for SRP

Announce: https://lore.kernel.org/linux-cve-announce/2024022405-CVE-2024-26600-44a2@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

If the external phy working together with phy-omap-usb2 does not
implement send_srp(), we may still attempt to call it.
It causes a NULL pointer dereference bug.

Introduced by commit 657b306 ("usb: phy: add a new driver for omap
usb2 phy") in 3.7-rc1.
Fixed in 6.8-rc3.

Fixed status
mainline: [7104ba0f1958adb250319e68a15eff89ec4fd36d]
stable/4.19: [486218c11e8d1c8f515a3bdd70d62203609d4b6b]
stable/5.10: [be3b82e4871ba00e9b5d0ede92d396d579d7b3b3]
stable/5.15: [8cc889b9dea0579726be9520fcc766077890b462]
stable/6.1: [0430bfcd46657d9116a26cd377f112cbc40826a4]
stable/6.6: [14ef61594a5a286ae0d493b8acbf9eac46fd04c4]
stable/6.7: [396e17af6761b3cc9e6e4ca94b4de7f642bfece1]

CVE-2024-26601: ext4: regenerate buddy after block freeing failed if
under fc replay

Announce: https://lore.kernel.org/linux-cve-announce/2024022411-CVE-2024-26601-b6ac@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
ext4: regenerate buddy after block freeing failed if under fc replay
This
mostly reverts commit 6bd97bf273bd ("ext4: remove redundant
mb_regenerate_buddy()") and reintroduces mb_regenerate_buddy(). Based
on code in
mb_free_blocks(), fast commit replay can end up marking as free blocks
that are already marked as such. This causes corruption of the buddy
bitmap so we need to regenerate it in that case.

Introduced by commit 6bd97bf ("ext4: remove redundant
mb_regenerate_buddy()") in 5.11-rc1.
This commit was backported to 5.10. However, 5.4, 4.19, and 4.4 are
not affected.
Fixed in 6.8-rc3.

Fixed status
mainline: [c9b528c35795b711331ed36dc3dbee90d5812d4e]
stable/6.1: [78327acd4cdc4a1601af718b781eece577b6b7d4]
stable/6.6: [ea42d6cffb0dd27a417f410b9d0011e9859328cb]
stable/6.7: [6b0d48647935e4b8c7b75d1eccb9043fcd4ee581]

CVE-2024-26602: sched/membarrier: reduce the ability to hammer on sys_membarrier

Announce: https://lore.kernel.org/linux-cve-announce/2024022414-CVE-2024-26602-5e76@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
sched/membarrier: reduce the ability to hammer on sys_membarrier On
some systems,
sys_membarrier can be very expensive, causing overall slowdowns for
everything. So put a lock on the path in order to serialize the
accesses to
prevent the ability for this to be called at too high of a frequency
and saturate the machine.

Introduced by commit c5f58bd ("membarrier: Provide GLOBAL_EXPEDITED
command") in 4.16-rc1.
Linux 4.4 is not affected.
Fixed in 6.8-rc6.

Fixed status
mainline: [944d5fe50f3f03daacfea16300e656a1691c4a23]
stable/4.19: [3cd139875e9a7688b3fc715264032620812a5fa3]
stable/5.10: [db896bbe4a9c67cee377e5f6a743350d3ae4acf6]
stable/5.15: [50fb4e17df319bb33be6f14e2a856950c1577dee]
stable/6.1: [24ec7504a08a67247fbe798d1de995208a8c128a]
stable/6.6: [b6a2a9cbb67545c825ec95f06adb7ff300a2ad71]
stable/6.7: [c5b2063c65d05e79fad8029324581d86cfba7eea]

CVE-2024-26603: x86/fpu: Stop relying on userspace for info to fault
in xsave buffer

Announce: https://lore.kernel.org/linux-cve-announce/2024022415-CVE-2024-26603-42c2@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Before this change, the expected size of the user space buffer was
taken from fx_sw->xstate_size. fx_sw->xstate_size can be changed
from user-space, so it is possible construct a sigreturn frame where:

 * fx_sw->xstate_size is smaller than the size required by valid bits in
   fx_sw->xfeatures.
 * user-space unmaps parts of the sigrame fpu buffer so that not all of
   the buffer required by xrstor is accessible.

In this case, xrstor tries to restore and accesses the unmapped area
which results in a fault. But fault_in_readable succeeds because buf +
fx_sw->xstate_size is within the still mapped area, so it goes back and
tries xrstor again. It will spin in this loop forever.

Instead, fault in the maximum size which can be touched by XRSTOR (taken
from fpstate->user_size).

Introduced by commit fcb3635 ("x86/fpu/signal: Handle #PF in the
direct restore path") in 5.14-rc1.
This commit is not backported to older stable kernels.
Fixed in 6.8-rc4.

Fixed status
mainline: [d877550eaf2dc9090d782864c96939397a3c6835]
stable/6.1: [627339cccdc9166792ecf96bc3c9f711a60ce996]
stable/6.6: [b2479ab426cef7ab79a13005650eff956223ced2]
stable/6.7: [627e28cbb65564e55008315d9e02fbb90478beda]

CVE-2024-26604: Revert "kobject: Remove redundant checks for whether
ktype is NULL"

Announce: https://lore.kernel.org/linux-cve-announce/2024022416-CVE-2024-26604-71a3@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
Revert "kobject: Remove redundant checks for whether ktype is NULL"
This reverts commit 1b28cb81dab7c1eedc6034206f4e8d644046ad31. It is
reported to cause problems, so revert it for now until the root cause
can be found.

Introduced by commit 1b28cb8 ("kobject: Remove redundant checks for
whether ktype is NULL") in 6.6-rc1.
This commit is not backported to older stable kernels.
Fixed in 6.8-rc5.

Fixed status
mainline: [3ca8fbabcceb8bfe44f7f50640092fd8f1de375c]
stable/6.6: [7f414d306320f837cc3df96cf52161cb8290fb1b]
stable/6.7: [b746d52ce7bcac325a2fa264216ead85b7fbbfaa]

CVE-2024-26605: PCI/ASPM: Fix deadlock when enabling ASPM

Announce: https://lore.kernel.org/linux-cve-announce/2024022419-CVE-2024-26605-7b06@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

A last minute revert in 6.7-final introduced a potential deadlock when
enabling ASPM during probe of Qualcomm PCIe controllers as reported by
lockdep.

Introduced by commit f93e71a ("Revert "PCI/ASPM: Remove
pcie_aspm_pm_state_change()"") in 6.7.
This commit was backported to 5.15 and 6.1. 5.10, 5.4, 4.19, 4.4 are
not affected.
Fixed in 6.8-rc3.

Fixed status
mainline: [1e560864159d002b453da42bd2c13a1805515a20]
stable/6.7: [ef90508574d7af48420bdc5f7b9a4f1cdd26bc70]

CVE-2023-52465: power: supply: Fix null pointer dereference in smb2_probe

Announce: https://lore.kernel.org/linux-cve-announce/2024022539-CVE-2023-52465-2e75@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

devm_kasprintf and devm_kzalloc return a pointer to dynamically
allocated memory which can be NULL upon failure.

Introduced by commit 8648aeb ("power: supply: add Qualcomm PMI8998
SMB2 Charger driver") in 6.5-rc1.
This commit is not backported to older stable kernels.
Fixed in 6.8-rc1.

Fixed status
mainline: [88f04bc3e737155e13caddf0ba8ed19db87f0212]
stable/6.6: [e2717302fbc20f148bcda362facee0444b949a3a]
stable/6.7: [bd3d2ec447ede9da822addf3960a5f4275e3ae76]

CVE-2023-52466: PCI: Avoid potential out-of-bounds read in
pci_dev_for_each_resource()

Announce: https://lore.kernel.org/linux-cve-announce/2024022544-CVE-2023-52466-fea5@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Coverity complains that pointer in the pci_dev_for_each_resource() may be
wrong, i.e., might be used for the out-of-bounds read.

There is no actual issue right now because we have another check afterwards
and the out-of-bounds read is not being performed. In any case it's better
code with this fixed, hence the proposed change.

As Jonas pointed out "It probably makes the code slightly less performant
as res will now be checked for being not NULL (which will always be true),
but I doubt it will be significant (or in any hot paths)."

Introduced by commit 09cc900 ("PCI: Introduce
pci_dev_for_each_resource()") in 6.4-rc1.
This commit is not backported to older stable kernels.
Fixed in 6.8-rc1.

Fixed status
mainline: [3171e46d677a668eed3086da78671f1e4f5b8405]
stable/6.6: [5b3e25efe16e06779a9a7c7610217c1b921ec179]
stable/6.7: [bd26159dcaaa3e9a927070efd348e7ce7e5ee933]

CVE-2023-52467: mfd: syscon: Fix null pointer dereference in
of_syscon_register()

Announce: https://lore.kernel.org/linux-cve-announce/2024022544-CVE-2023-52467-434b@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

kasprintf() returns a pointer to dynamically allocated memory which
can be NULL upon failure.

Introduced by commit e15d7f2 ("mfd: syscon: Use a unique name with
regmap_config") in 5.9-rc1.
This commit is not backported to older stable kernels.
Fixed in 6.8-rc1.

Fixed status
mainline: [41673c66b3d0c09915698fec5c13b24336f18dd1]
stable/5.10: [927626a2073887ee30ba00633260d4d203f8e875]
stable/5.15: [c3e3a2144bf50877551138ffce9f7aa6ddfe385b]
stable/6.1: [527e8c5f3d00299822612c495d5adf1f8f43c001]
stable/6.6: [3ef1130deee98997275904d9bfc37af75e1e906c]
stable/6.7: [7f2c410ac470959b88e03dadd94b7a0b71df7973]

CVE-2023-52468: class: fix use-after-free in class_register()

Announce: https://lore.kernel.org/linux-cve-announce/2024022545-CVE-2023-52468-59a2@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

The lock_class_key is still registered and can be found in
lock_keys_hash hlist after subsys_private is freed in error
handler path.A task who iterate over the lock_keys_hash later may
cause use-after-free.So fix that up and unregister
the lock_class_key before kfree(cp).

On our platform, a driver fails to kset_register because of creating
duplicate filename '/class/xxx'.With Kasan enabled,
it prints a invalid-access bug report.

Introduced by commit dcfbb67 ("driver core: class: use lock_class_key
already present in struct subsys_private") in 6.4-rc1.
This commit is not backported to older stable kernels.
Fixed in 6.8-rc1.

Fixed status
mainline: [93ec4a3b76404bce01bd5c9032bef5df6feb1d62]
stable/6.6: [b57196a5ec5e4c0ffecde8348b085b778c7dce04]
stable/6.7: [0f1486dafca3398c4c46b9f6e6452fa27e73b559]

CVE-2023-52469: drivers/amd/pm: fix a use-after-free in kv_parse_power_table

Announce: https://lore.kernel.org/linux-cve-announce/2024022546-CVE-2023-52469-5141@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

When ps allocated by kzalloc equals to NULL, kv_parse_power_table
frees adev->pm.dpm.ps that allocated before. However, after the control
flow goes through the following call chains:

kv_parse_power_table
  |-> kv_dpm_init
        |-> kv_dpm_sw_init
          |-> kv_dpm_fini

The adev->pm.dpm.ps is used in the for loop of kv_dpm_fini after its
first free in kv_parse_power_table and causes a use-after-free bug.

Introduced by commit in a2e73f5 ("drm/amdgpu: Add support for CIK
parts") in 4.2-rc1.
Fixed in 6.8-rc1.

Fixed status
mainline: [28dd788382c43b330480f57cd34cde0840896743]
stable/4.19: [8a27d9d9fc9b5564b8904c3a77a7dea482bfa34e]
stable/5.10: [520e213a0b97b64735a13950e9371e0a5d7a5dc3]
stable/5.15: [b6dcba02ee178282e0d28684d241e0b8462dea6a]
stable/5.4: [8b55b06e737feb2a645b0293ea27e38418876d63]
stable/6.1: [35fa2394d26e919f63600ce631e6aefc95ec2706]
stable/6.6: [95084632a65d5c0d682a83b55935560bdcd2a1e3]
stable/6.7: [3426f059eacc33ecc676b0d66539297e1cfafd02]

CVE-2023-52470: drm/radeon: check the alloc_workqueue return value in
radeon_crtc_init()

Announce: https://lore.kernel.org/linux-cve-announce/2024022546-CVE-2023-52470-44d1@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

check the alloc_workqueue return value in radeon_crtc_init() to avoid
null-ptr-deref.

Introduced by commit fa7f517 ("drm/radeon: rework page flip handling
v4") in 3.16-rc1.
Fixed in 6.8-rc1.

Fixed status
mainline: [7a2464fac80d42f6f8819fed97a553e9c2f43310]
stable/4.19: [21b1645660717d6126dd4866c850fcc5c4703a41]
stable/5.10: [57ca7984806d79b38af528de88fd803babf27feb]
stable/5.15: [14bbfaa5df273b26cde6707f6e655585700e6fe1]
stable/5.4: [5d12c5d75f7c78b83a738025947651ec5c95b4d4]
stable/6.1: [c4ff55408187f2595066967047363ca84e76db85]
stable/6.6: [0b813a6a0087451cb702b6eb841f10856f49d088]
stable/6.7: [fb2d8bc9b5e55848b8a7c3c028e2ee8d49f28f97]

CVE-2023-52471: ice: Fix some null pointer dereference issues in ice_ptp.c

Announce: https://lore.kernel.org/linux-cve-announce/2024022546-CVE-2023-52471-ab29@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
ice: Fix some null pointer dereference issues in ice_ptp.c
devm_kasprintf() returns a pointer to dynamically allocated memory
which can be NULL upon failure.

Introduced by commit d938a8c ("ice: Auxbus devices & driver for E822
TS") in 6.7-rc1.
This commit is not backported to older stable kernels.
Fixed in 6.8-rc1.

Fixed status
mainline: [3027e7b15b02d2d37e3f82d6b8404f6d37e3b8cf]
stable/6.7: [3cd9b9bee33f39f6c6d52360fe381b89a7b12695]

CVE-2023-52472: crypto: rsa - add a check for allocation failure

Announce: https://lore.kernel.org/linux-cve-announce/2024022547-CVE-2023-52472-fa03@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
crypto: rsa - add a check for allocation failure Static checkers
insist that the mpi_alloc() allocation can fail so add a check to
prevent a NULL dereference. Small allocations like this can't actually
fail in current kernels, but adding a check is very simple and makes
the static checkers happy.

Introduced by commit 6637e11 ("crypto: rsa - allow only odd e and
restrict value in FIPS mode") in 6.5-rc1.
This commit is not backported to older stable kernels.
Fixed in 6.8-rc1.

Fixed status
mainline: [d872ca165cb67112f2841ef9c37d51ef7e63d1e4]
stable/6.6: [2831f4d3bfa68e64c5f83e96688be779c87b3511]
stable/6.7: [95ad8b6879e2e49d02e3bfc0e1fb46421633fe2a]

CVE-2023-52473: thermal: core: Fix NULL pointer dereference in zone
registration error path

Announce: https://lore.kernel.org/linux-cve-announce/2024022547-CVE-2023-52473-c3cc@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
thermal: core: Fix NULL pointer dereference in zone registration error
path If device_register() in thermal_zone_device_register_with_trips()
returns an error, the tz variable is set to NULL and subsequently
dereferenced in kfree(tz->tzp). Commit adc8749b150c
("thermal/drivers/core: Use put_device() if device_register() fails")
added the tz = NULL
assignment in question to avoid a possible double-free after dropping
the reference to the zone device. However, after commit 4649620d9404
("thermal: core: Make thermal_zone_device_unregister() return after
freeing the zone"), that assignment has become redundant, because
dropping
the reference to the zone device does not cause the zone object to be
freed any more. Drop it to address the NULL pointer dereference.

Introduced by commit 3d439b1 ("thermal/core: Alloc-copy-free the
thermal zone parameters structure") in 6.4-rc1.
This commit is not backported to older stable kernels.
Fixed in 6.8-rc1.

Fixed status
mainline: [04e6ccfc93c5a1aa1d75a537cf27e418895e20ea]
stable/6.6: [335176dd8ebaca6493807dceea33c478305667fa]
stable/6.7: [02871710b93058eb1249d5847c0b2d1c2c3c98ae]

CVE-2021-46904: net: hso: fix null-ptr-deref during tty device unregistration

Announce: https://lore.kernel.org/linux-cve-announce/2024022555-CVE-2021-46904-d49f@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
net: hso: fix null-ptr-deref during tty device unregistration Multiple
ttys
try to claim the same the minor number causing a double unregistration
of the same device. The first unregistration succeeds but the next one
results in a null-ptr-deref. The get_free_serial_index() function
returns an available minor number but doesn't assign it immediately.
The assignment is done by the caller later. But before this
assignment, calls to get_free_serial_index() would return the same
minor number.
Fix this by modifying get_free_serial_index to assign the minor number
immediately after one is found to be and rename it to obtain_minor()
to
better reflect what it does. Similary, rename set_serial_by_index() to
release_minor() and modify it to free up the minor number of the
given hso_serial. Every obtain_minor() should have corresponding
release_minor() call.

Introduced by commit 72dc1c0 ("HSO: add option hso driver") in 2.6.27-rc1.
Fixed in 5.12-rc7.

Fixed status
cip/4.4: [a462067d7c8e6953a733bf5ade8db947b1bb5449]
cip/4.4-rt: [a462067d7c8e6953a733bf5ade8db947b1bb5449]
cip/4.4-st: [a462067d7c8e6953a733bf5ade8db947b1bb5449]
mainline: [8a12f8836145ffe37e9c8733dce18c22fb668b66]
stable/4.14: [caf5ac93b3b5d5fac032fc11fbea680e115421b4]
stable/4.19: [92028d7a31e55d53e41cff679156b9432cffcb36]
stable/4.4: [a462067d7c8e6953a733bf5ade8db947b1bb5449]
stable/4.9: [145c89c441d27696961752bf51b323f347601bee]
stable/5.10: [dc195928d7e4ec7b5cfc6cd10dc4c8d87a7c72ac]
stable/5.4: [4a2933c88399c0ebc738db39bbce3ae89786d723]

CVE-2021-46905: net: hso: fix NULL-deref on disconnect regression

Announce: https://lore.kernel.org/linux-cve-announce/2024022557-CVE-2021-46905-6507@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
net: hso: fix NULL-deref on disconnect regression Commit
8a12f8836145 ("net: hso: fix null-ptr-deref during tty device
unregistration") fixed the racy minor allocation reported by syzbot,
but introduced an unconditional NULL-pointer dereference on every
disconnect instead. Specifically, the serial device table must no
longer
be accessed after the minor has been released by hso_serial_tty_unregister().

Introduced by commit 8a12f88 ("net: hso: fix null-ptr-deref during tty
device unregistration") in v5.12-rc7.
Fixed in 5.13-rc1.

Fixed status
cip/4.4: [5871761c5f0f20d6e98bf3b6bd7486d857589554]
cip/4.4-rt: [5871761c5f0f20d6e98bf3b6bd7486d857589554]
cip/4.4-st: [5871761c5f0f20d6e98bf3b6bd7486d857589554]
mainline: [2ad5692db72874f02b9ad551d26345437ea4f7f3]
stable/4.14: [24b699bea7553fc0b98dad9d864befb6005ac7f1]
stable/4.19: [5c17cfe155d21954b4c7e2a78fa771cebcd86725]
stable/4.4: [5871761c5f0f20d6e98bf3b6bd7486d857589554]
stable/4.9: [0c71d4c89559f72cec2592d078681a843bce570e]
stable/5.10: [90642ee9eb581a13569b1c0bd57e85d962215273]
stable/5.4: [d7fad2ce15bdbbd0fec3ebe999fd7cab2267f53e]

CVE-2022-48626: moxart: fix potential use-after-free on remove path

Announce: https://lore.kernel.org/linux-cve-announce/2024022558-CVE-2022-48626-8a90@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
moxart: fix potential use-after-free on remove path It was reported
that
the mmc host structure could be accessed after it was freed in
moxart_remove(), so fix this by saving the base register of the device
and using
it instead of the pointer dereference.

Fixed in 5.17-rc4.

Fixed status
cip/4.4: [f86b87424a132623dd8d15801c578b2d5e351060]
cip/4.4-rt: [f86b87424a132623dd8d15801c578b2d5e351060]
cip/4.4-st: [f86b87424a132623dd8d15801c578b2d5e351060]
mainline: [bd2db32e7c3e35bd4d9b8bbff689434a50893546]
stable/4.14: [e6f580d0b3349646d4ee1ce0057eb273e8fb7e2e]
stable/4.19: [9c25d5ff1856b91bd4365e813f566cb59aaa9552]
stable/4.9: [f5dc193167591e88797262ec78515a0cbe79ff5f]
stable/5.10: [be93028d306dac9f5b59ebebd9ec7abcfc69c156]
stable/5.15: [af0e6c49438b1596e4be8a267d218a0c88a42323]
stable/5.4: [3a0a7ec5574b510b067cfc734b8bdb6564b31d4e]

CVE-2020-36775: f2fs: fix to avoid potential deadlock

Announce: https://lore.kernel.org/linux-cve-announce/2024022602-CVE-2020-36775-1cbe@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Using f2fs_trylock_op() in f2fs_write_compressed_pages() to avoid
potential deadlock like we did in f2fs_write_single_data_page().

Fixed in 5.7-rc1.

Fixed status
mainline: [df77fbd8c5b222c680444801ffd20e8bbc90a56e]
stable/5.4: [0478ccdc8ea016de1ebaf6fe6da0275c2b258c5b]

CVE-2023-52474: IB/hfi1: Fix bugs with non-PAGE_SIZE-end multi-iovec
user SDMA requests

Announce: https://lore.kernel.org/linux-cve-announce/2024022603-CVE-2023-52474-6691@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

There is bugs in hfi1 user SDMA request processing causing data
corruption due to mishandling iovec lengths and incorrect advancement
across iovecs,
alongside issues in SDMA pin cache management, including overlapping
pinnings and refcount mismanagement, necessitating fixes to prevent
data loss.

Introduced by commit 7be8567 ("IB/hfi1: Don't remove RB entry when not
needed.") in 4.14-rc1 and 7724105 ("IB/hfi1: add driver files") in
v4.3-rc1.
Fixed in 6.4-rc1.

Fixed status
mainline: [00cbce5cbf88459cd1aa1d60d0f1df15477df127]
stable/5.10: [9c4c6512d7330b743c4ffd18bd999a86ca26db0d]
stable/5.15: [a2bd706ab63509793b5cd5065e685b7ef5cba678]
stable/6.1: [dce59b5443700fbd0d2433ec6e4d4cf063448844]

CVE-2024-26606: binder: signal epoll threads of self-work

Announce: https://lore.kernel.org/linux-cve-announce/2024022620-CVE-2024-26606-64b6@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
binder: signal epoll threads of self-work In (e)poll mode, threads
often depend
on I/O events to determine when data is ready for consumption. Within
binder, a thread may initiate a command via BINDER_WRITE_READ without
a
read buffer and then make use of epoll_wait() or similar to consume
any responses afterwards. It is then crucial that epoll threads are
signaled
via wakeup when they queue their own work. Otherwise, they risk
waiting indefinitely for an event leaving their work unhandled. What
is worse,
subsequent commands won't trigger a wakeup either as the thread has
pending work.

Introduced by commit 457b9a6 ("Staging: android: add binder driver")
in 2.6.29-rc1.
Fixed in 6.8-rc3.

Fixed status
mainline: [97830f3c3088638ff90b20dfba2eb4d487bf14d7]
stable/4.19: [dd64bb8329ce0ea27bc557e4160c2688835402ac]
stable/5.10: [a423042052ec2bdbf1e552e621e6a768922363cc]
stable/5.15: [82722b453dc2f967b172603e389ee7dc1b3137cc]
stable/5.4: [42beab162dcee1e691ee4934292d51581c29df61]
stable/6.1: [90e09c016d72b91e76de25f71c7b93d94cc3c769]
stable/6.6: [a7ae586f6f6024f490b8546c8c84670f96bb9b68]
stable/6.7: [93b372c39c40cbf179e56621e6bc48240943af69]

CVE-2019-25160: netlabel: fix out-of-bounds memory accesses

Announce: https://lore.kernel.org/linux-cve-announce/2024022657-CVE-2019-25160-e487@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

There are two array out-of-bounds memory accesses, one in
cipso_v4_map_lvl_valid(), the other in netlbl_bitmap_walk().  Both
errors are embarassingly simple, and the fixes are straightforward.

As a FYI for anyone backporting this patch to kernels prior to v4.8,
you'll want to apply the netlbl_bitmap_walk() patch to
cipso_v4_bitmap_walk() as netlbl_bitmap_walk() doesn't exist before Linux v4.8.

Introduced by commit 446fda4 ("[NetLabel]: CIPSOv4 engine") in 2.6.19-rc1 and
3faa8f9 ("netlabel: Move bitmap manipulation functions to the NetLabel
core.") in 4.8-rc1.
Fixed in 5.0.

Fixed status
cip/4.4: [dc18101f95fa6e815f426316b8b9a5cee28a334e]
cip/4.4-rt: [dc18101f95fa6e815f426316b8b9a5cee28a334e]
cip/4.4-st: [dc18101f95fa6e815f426316b8b9a5cee28a334e]
mainline: [5578de4834fe0f2a34fedc7374be691443396d1f]
stable/4.19: [e3713abc4248aa6bcc11173d754c418b02a62cbb]

CVE-2019-25161: drm/amd/display: prevent memory leak

Announce: https://lore.kernel.org/linux-cve-announce/2024022601-CVE-2019-25161-f77d@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

This CVE is rejected.

In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: prevent memory leak In dcn*_create_resource_pool
the allocated memory should be released if construct pool fails.

Fixed in 5.4-rc1.

Fixed status
mainline: [104c307147ad379617472dd91a5bcb368d72bd6d]
stable/4.19: [60e1b411bf0fd9fda2d2de7f45dc3b1d9960b85e]

CVE-2019-25162: i2c: Fix a potential use after free

Announce: https://lore.kernel.org/linux-cve-announce/2024022602-CVE-2019-25162-70ae@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
i2c: Fix a potential use after free Free the adap structure only
after we are done using it. This patch just moves the put_device()
down a bit to avoid the use after free. [wsa: added comment to
the code, added Fixes tag]

Introduced by commit 611e12e ("i2c: core: manage i2c bus device
refcount in i2c_[get|put]_adapter") in 4.3-rc1.
Fixed in 6.0-rc1.

Fixed status
mainline: [e4c72c06c367758a14f227c847f9d623f1994ecf]
stable/4.19: [23a191b132cd87f746c62f3dc27da33683d85829]
stable/5.10: [81cb31756888bb062e92d2dca21cd629d77a46a9]
stable/5.15: [35927d7509ab9bf41896b7e44f639504eae08af7]
stable/5.4: [871a1e94929a27bf6e2cd99523865c840bbc2d87]

CVE-2021-46906: HID: usbhid: fix info leak in hid_submit_ctrl

Announce: https://lore.kernel.org/linux-cve-announce/2024022603-CVE-2021-46906-636c@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
HID: usbhid: fix info leak in hid_submit_ctrl In hid_submit_ctrl(),
the way of calculating the report length doesn't take into account
that report->size can be zero. When running the syzkaller reproducer,
a report of size 0 causes hid_submit_ctrl() to calculate
transfer_buffer_length as 16384. When this urb is passed to the usb
core layer,
KMSAN reports an info leak of 16384 bytes. To fix this, first modify
hid_report_len() to account for the zero report size case by using
DIV_ROUND_UP for the division. Then, call it from hid_submit_ctrl().

Fixed in 5.13-rc1.

Fixed status
cip/4.4: [c5d3c142f2d57d40c55e65d5622d319125a45366]
cip/4.4-rt: [c5d3c142f2d57d40c55e65d5622d319125a45366]
cip/4.4-st: [c5d3c142f2d57d40c55e65d5622d319125a45366]
mainline: [6be388f4a35d2ce5ef7dbf635a8964a5da7f799f]
stable/4.19: [0e280502be1b003c3483ae03fc60dea554fcfa82]
stable/5.10: [b1e3596416d74ce95cc0b7b38472329a3818f8a9]
stable/5.4: [7f5a4b24cdbd7372770a02f23e347d7d9a9ac8f1]

CVE-2020-36776: thermal/drivers/cpufreq_cooling: Fix slab OOB issue

Announce: https://lore.kernel.org/linux-cve-announce/20240227184057.2368370-1-gregkh@linuxfoundation.org/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Slab OOB issue is scanned by KASAN in cpu_power_to_freq(). If power is
limited below the power of OPP0 in EM table,
it will cause slab out-of-bound issue with negative array index.
Return the lowest frequency if limited power cannot found a suitable
OPP in EM table to fix this issue.

Introduced by commit 371a3bc ("thermal/drivers/cpufreq_cooling: Fix
wrong frequency converted from power") in 5.8-rc4.
This patci is backported to 5.4 and 4.19. Linux 4.4 is not affected.
Fixed in 5.13-rc1.

Fixed status
mainline: [34ab17cc6c2c1ac93d7e5d53bb972df9a968f085]
stable/5.10: [c24a20912eef00587416628149c438e885eb1304]

CVE-2020-36777: media: dvbdev: Fix memory leak in dvb_media_device_free()

Announce: https://lore.kernel.org/linux-cve-announce/20240227184057.2368370-2-gregkh@linuxfoundation.org/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
media: dvbdev: Fix memory leak in dvb_media_device_free()
dvb_media_device_free() is leaking memory. Free
`dvbdev->adapter->conn` before setting it to NULL, as documented in
include/media/media-device.h: "The media_entity instance itself must
be freed explicitly by the driver if required."

Introduced by commit 0230d60 ("[media] dvbdev: Add RF connect0or if
needed") in 4.5-rc1.
This patch is not backported to 4.4.
Fixed in 5.13-rc1.

Fixed status
mainline: [bf9a40ae8d722f281a2721779595d6df1c33a0bf]
stable/4.19: [cd89f79be5d553c78202f686e8e4caa5fbe94e98]
stable/5.10: [43263fd43083e412311fa764cd04a727b0c6a749]
stable/5.4: [9185b3b1c143b8da409c19ac5a785aa18d67a81b]

CVE-2021-46925: net/smc: fix kernel panic caused by race of smc_sock

Announce: https://lore.kernel.org/linux-cve-announce/2024022748-CVE-2021-46925-c422@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

A crash occurs when smc_cdc_tx_handler() tries to access smc_sock but
smc_release() has already freed it.

Introduced by commit 5f08318 ("smc: connection data control (CDC)") in 4.11-rc1.
This patch is not backported to 4.4.
Fixed in 5.16-rc8

Fixed status
mainline: [349d43127dac00c15231e8ffbcaabd70f7b0e544]
stable/5.10: [e8a5988a85c719ce7205cb00dcf0716dcf611332]
stable/5.15: [b85f751d71ae8e2a15e9bda98852ea9af35282eb]

CVE-2021-46926: ALSA: hda: intel-sdw-acpi: harden detection of controller

Announce: https://lore.kernel.org/linux-cve-announce/2024022748-CVE-2021-46926-9967@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
ALSA: hda: intel-sdw-acpi: harden detection of controller The
existing code currently sets a pointer to an ACPI handle before
checking that it's actually a SoundWire controller. This can lead
to issues where the graph walk continues and eventually fails, but the
pointer was set already. This patch changes the logic so
that the information provided to the caller is set when a controller is found.

Introduced commit is not determined.
The sdw_intel_acpi_cb() is introcued by commit d62a7d41 ("soundwire:
intel: Add Intel init module") in 4.16-rc1.
Fixed in 5.16-rc7.

Fixed status
mainline: [385f287f9853da402d94278e59f594501c1d1dad]
stable/5.15: [cce476954401e3421afafb25bbaa926050688b1d]

CVE-2021-46928: parisc: Clear stale IIR value on instruction access rights trap

Announce: https://lore.kernel.org/linux-cve-announce/2024022748-CVE-2021-46926-9967@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
parisc: Clear stale IIR value on instruction access rights trap
When a trap 7 (Instruction access rights) occurs, this means the CPU
couldn't execute an instruction due to missing execute permissions
on the memory region. In this case it seems the CPU didn't even
fetched the instruction from memory and thus did not store it in the
cr19 (IIR) register before calling the trap handler. So, the trap
handler will find some random old stale value in cr19. This patch
simply overwrites the stale IIR value with a constant magic "bad food"
value (0xbaadf00d), in the hope people don't start to try to
understand the various random IIR values in trap 7 dumps.

Introduced commit is not determined.
Patch may be able to apply to 4.19 and 4.4.
Fixed in 5.16-rc7.

Fixed status
mainline: [484730e5862f6b872dca13840bed40fd7c60fa26]
stable/5.10: [d01e9ce1af6116f812491d3d3873d204f10ae0b8]
stable/5.15: [e96373f0a5f484bc1e193f9951dcb3adf24bf3f7]

CVE-2021-46938: dm rq: fix double free of blk_mq_tag_set in dev remove
after table load fails

Announce: https://lore.kernel.org/linux-cve-announce/20240227184057.2368370-3-gregkh@linuxfoundation.org/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

When loading a device-mapper table for a request-based mapped device,
and the allocation/initialization of the blk_mq_tag_set for the device
fails, a following device remove will cause a double free.

Introduced by commit 1c357a1 ("dm: allocate blk_mq_tag_set rather than
embed in mapped_device") in 4.6-rc1.
This patch is not backported to 4.4.
Fixed in 5.13-rc1.

Fixed status
mainline: [8e947c8f4a5620df77e43c9c75310dc510250166]
stable/4.19: [772b9f59657665af3b68d24d12b9d172d31f0dfb]
stable/5.10: [1cb02dc76f4c0a2749a02b26469512d6984252e9]
stable/5.4: [a992a283c0b77d0a7c2c348add0e6a21fb1dab67]

CVE-2021-46939: tracing: Restructure trace_clock_global() to never block

Announce: https://lore.kernel.org/linux-cve-announce/20240227184057.2368370-4-gregkh@linuxfoundation.org/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

It was reported that a fix to the ring buffer recursion detection
would cause a hung machine when performing suspend / resume testing.

Introduced by commit b02414c ("ring-buffer: Fix recursion protection
transitions between interrupt context") # started showing the problem
in 5.10-rc3
and 14131f2 ("tracing: implement trace_clock_*() APIs") in 2.6.30-rc1.
The commit b02414c is backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
cip/4.4: [91ca6f6a91f679c8645d7f3307e03ce86ad518c4]
cip/4.4-rt: [91ca6f6a91f679c8645d7f3307e03ce86ad518c4]
cip/4.4-st: [91ca6f6a91f679c8645d7f3307e03ce86ad518c4]
mainline: [aafe104aa9096827a429bc1358f8260ee565b7cc]
stable/4.19: [d43d56dbf452ccecc1ec735cd4b6840118005d7c]
stable/5.10: [a33614d52e97fc8077eb0b292189ca7d964cc534]
stable/5.4: [c64da3294a7d59a4bf6874c664c13be892f15f44]

CVE-2021-46940: tools/power turbostat: Fix offset overflow issue in
index converting

Announce: https://lore.kernel.org/linux-cve-announce/20240227184057.2368370-5-gregkh@linuxfoundation.org/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
tools/power turbostat: Fix offset overflow issue in index converting
The idx_to_offset() function returns type int (32-bit signed), but
MSR_PKG_ENERGY_STAT is u32 and would be interpreted as a negative
number.
The end result is that it hits the if (offset < 0) check in
update_msr_sum() which prevents the timer callback from updating the
stat in
the background when long durations are used. The similar issue exists
in offset_to_idx() and update_msr_sum(). Fix this issue by converting
t
he 'int' to 'off_t' accordingly.

Introduced by commit 9972d5d ("tools/power turbostat: Enable
accumulate RAPL display") in 5.10-rc4.
This patch is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [13a779de4175df602366d129e41782ad7168cef0]
stable/5.10: [ea6803ff2cd1a2d7d880256bf562172b708a76ff]

CVE-2021-46941: usb: dwc3: core: Do core softreset when switch mode

Announce: https://lore.kernel.org/linux-cve-announce/20240227184057.2368370-6-gregkh@linuxfoundation.org/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

A lockup issue was found in HiKey960 platform because lacks of do
required steps  to switch mode for DRD controller.

Introduced by commit 41ce145 ("usb: dwc3: core: make dwc3_set_mode()
work properly") in 4.12-rc1.
This commit is not backported to 4.4.
Fixed in 5.13-rc1.

Fixed status
mainline: [f88359e1588b85cf0e8209ab7d6620085f3441d9]
stable/5.10: [fce7bbcd07d59ac30dba8ce225316b3b4c1c7b50]

CVE-2021-46942: io_uring: fix shared sqpoll cancellation hangs

Announce: https://lore.kernel.org/linux-cve-announce/20240227184057.2368370-7-gregkh@linuxfoundation.org/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

We call io_uring_cancel_sqpoll() one by one for each ctx either in
sq_thread() itself or via task works, and it's intended to cancel all
requests of a specified context. However the function uses per-task
counters to track the number of inflight requests, so it counts more
requests than available via currect io_uring ctx and goes to sleep for
them to appear (e.g. from IRQ), that will never happen.
Cancel a bit more than before, i.e. all ctxs that share sqpoll and
continue to use shared counters. Don't forget that we should not
remove ctx from the list before running that task_work sqpoll-cancel,
otherwise the function wouldn't be able to find the context and will
hang.

Introduced by commit 37d1e2e ("io_uring: move SQPOLL thread io-wq
forked worker") in 5.12-rc1dontuse.
This patch is not backported to 5.10. The io_uring is introcued in 5.1
so 4.x kernels are not affected.
Fixed in 5.13-rc1.

Fixed status
mainline: [734551df6f9bedfbefcd113ede665945e9de0b99]

CVE-2021-46943: media: staging/intel-ipu3: Fix set_fmt error handling

Announce: https://lore.kernel.org/linux-cve-announce/20240227184057.2368370-8-gregkh@linuxfoundation.org/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

If there in an error during a set_fmt, do not overwrite the previous
sizes with the invalid config.
Without this patch, v4l2-compliance ends up allocating 4GiB of RAM and
causing the following OOPs
[   38.662975] ipu3-imgu 0000:00:05.0: swiotlb buffer is full (sz: 4096 bytes)
[   38.662980] DMA: Out of SW-IOMMU space for 4096 bytes at device 0000:00:05.0
[   38.663010] general protection fault: 0000 [#1] PREEMPT SMP

Introduced by commit 6d5f26f ("media: staging/intel-ipu3-v4l: reduce
kernel stack usage") in 5.2-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [ad91849996f9dd79741a961fd03585a683b08356]
stable/5.10: [c6b81b897f6f9445d57f8d47c4e060ec21556137]
stable/5.4: [a03fb1e8a110658215a4cefc3e2ad53279e496a6]

CVE-2021-46944: media: staging/intel-ipu3: Fix memory leak in imu_fmt

Announce: https://lore.kernel.org/linux-cve-announce/20240227184057.2368370-9-gregkh@linuxfoundation.org/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
media: staging/intel-ipu3: Fix memory leak in imu_fmt We are losing
the reference to an allocated memory if try. Change the order of the
check to avoid that.

Introduced-by commit 6d5f26f ("media: staging/intel-ipu3-v4l: reduce
kernel stack usage") in 5.2-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [3630901933afba1d16c462b04d569b7576339223]
stable/5.10: [517f6f570566a863c2422b843c8b7d099474f6a9]
stable/5.4: [ff792ae52005c85a2d829c153e08d99a356e007d]

CVE-2021-46945: ext4: always panic when errors=panic is specified

Announce: https://lore.kernel.org/linux-cve-announce/20240227184057.2368370-10-gregkh@linuxfoundation.org/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
ext4: always panic when errors=panic is specified Before commit
014c9caa29d3
("ext4: make ext4_abort() use __ext4_error()"), the following series
of commands would trigger a panic: 1. mount /dev/sda -o
ro,errors=panic
test 2. mount /dev/sda -o remount,abort test After commit
014c9caa29d3, remounting a file system using the test mount option
"abort" will no
longer trigger a panic. This commit will restore the behaviour
immediately before commit 014c9caa29d3. (However, note that the Linux
kernel's
behavior has not been consistent; some previous kernel versions,
including 5.4 and 4.19 similarly did not panic after using the mount
option "abort".)
This also makes a change to long-standing behaviour; namely, the
following series commands will now cause a panic, when previously it
did not:
1. mount /dev/sda -o ro,errors=panic test
2. echo test > /sys/fs/ext4/sda/trigger_fs_error
However, this makes ext4's behaviour much more consistent, so this is
a good thing.

Introduced by commit 014c9ca ("ext4: make ext4_abort() use
__ext4_error()") in 5.11-rc1.
Thix commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [ac2f7ca51b0929461ea49918f27c11b680f28995]

CVE-2021-46946: ext4: fix check to prevent false positive report of
incorrect used inodes

Announce: https://lore.kernel.org/linux-cve-announce/20240227184057.2368370-11-gregkh@linuxfoundation.org/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Commit <50122847007> ("ext4: fix check to prevent initializing
reserved inodes") check the block group zero and prevent initializing
reserved
inodes. But in some special cases, the reserved inode may not all
belong to the group zero, it may exist into the second group if we
format
filesystem below.
  mkfs.ext4 -b 4096 -g 8192 -N 1024 -I 4096 /dev/sda
So, it will end up triggering a false positive report of a corrupted
file system. This patch fix it by avoid check reserved inodes if no
free
inode blocks will be zeroed.

Introduced by commit 5012284 ("ext4: fix check to prevent initializing
reserved inodes") in 4.18-rc7.
This commit is backported to 4.4.
Fixed in 5.13-rc1.

Fixed status
cip/4.4: [539ba4ebc467260225898e67ea53cbb73308f894]
cip/4.4-rt: [539ba4ebc467260225898e67ea53cbb73308f894]
cip/4.4-st: [539ba4ebc467260225898e67ea53cbb73308f894]
cip/5.10: [098b257563b959f4ca6c1d82fde0ee727792cb19]
cip/5.10-rt: [098b257563b959f4ca6c1d82fde0ee727792cb19]
mainline: [a149d2a5cabbf6507a7832a1c4fd2593c55fd450]
stable/4.19: [7687f5aba0f50c7ff8040e506bae184e59c8e7b8]
stable/5.10: [098b257563b959f4ca6c1d82fde0ee727792cb19]
stable/5.4: [9c61387630a54e35b96a90608aafd369ffb86f39]

CVE-2021-46947: sfc: adjust efx->xdp_tx_queue_count with the real
number of initialized queues

Announce: https://lore.kernel.org/linux-cve-announce/20240227184057.2368370-12-gregkh@linuxfoundation.org/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

efx->xdp_tx_queue_count is initially initialized to
num_possible_cpus() and is later used to allocate and traverse
efx->xdp_tx_queues lookup array. However,
we may end up not initializing all the array slots with real queues
during probing. This results, for example, in a NULL pointer
dereference, when running
"# ethtool -S <iface>".

Introduced by commit e26ca4b ("sfc: reduce the number of requested xdp
ev queues") in 5.12-rc1dontuse.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [99ba0ea616aabdc8e26259fd722503e012199a76]

CVE-2021-46948: sfc: farch: fix TX queue lookup in TX event handling

Announce: https://lore.kernel.org/linux-cve-announce/20240227184057.2368370-13-gregkh@linuxfoundation.org/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

We're starting from a TXQ label, not a TXQ type, so
efx_channel_get_tx_queue() is inappropriate (and could return NULL,
leading to panics).

Introduced by commit 1280479 ("sfc: decouple TXQ type from label") in 5.10-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [83b09a1807415608b387c7bc748d329fefc5617e]
stable/5.10: [bf2b941d0a6f2d3b9f5fa3c4c21bdd54f71ce253]

CVE-2021-46949: sfc: farch: fix TX queue lookup in TX flush done handling

Announce: https://lore.kernel.org/linux-cve-announce/20240227184057.2368370-14-gregkh@linuxfoundation.org/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

We're starting from a TXQ instance number ('qid'), not a TXQ type, so
efx_get_tx_queue() is inappropriate (and could return NULL, leading to
panics).

Introduced by commit 1280479 ("sfc: decouple TXQ type from label") in 5.10-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [5b1faa92289b53cad654123ed2bc8e10f6ddd4ac]
stable/5.10: [fb791572d6747ef385f628450f8d57cd132e6e5a]

CVE-2021-46950: md/raid1: properly indicate failure when ending a
failed write request

Announce: https://lore.kernel.org/linux-cve-announce/20240227184057.2368370-15-gregkh@linuxfoundation.org/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

This patch addresses a data corruption bug in raid1 arrays using
bitmaps. Without this fix, the bitmap bits for the failed I/O end up
being cleared.
Since we are in the failure leg of raid1_end_write_request, the
request either needs to be retried (R1BIO_WriteError) or failed
(R1BIO_Degraded).

Introduced by commit eeba680 ("md/raid1: end bio when the device
faulty") in 5.4-rc1.
This commit is backported to 4.19. Linux 4.4 is not affected.
Fixed in 5.13-rc1.

Fixed status
mainline: [2417b9869b81882ab90fd5ed1081a1cb2d4db1dd]
stable/4.19: [a6e17cab00fc5bf85472434c52ac751426257c6f]
stable/5.10: [661061a45e32d8b2cc0e306da9f169ad44011382]
stable/5.4: [6920cef604fa57f9409e3960413e9cc11f5c5a40]

CVE-2021-46951: tpm: efi: Use local variable for calculating final log size

Announce: https://lore.kernel.org/linux-cve-announce/20240227184057.2368370-16-gregkh@linuxfoundation.org/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

When tpm_read_log_efi is called multiple times, which happens when one
loads and unloads a TPM2 driver multiple times, then the global
variable efi_tpm_final_log_size will at some point become a negative
number due to the subtraction of final_events_preboot_size occurring
each time. Use a local variable to avoid this integer underflow.

Introduced by commit 166a280 ("tpm: Don't duplicate events from the
final event log in the TCG2 log") in 5.3-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [48cff270b037022e37835d93361646205ca25101]
stable/5.10: [60a01ecc9f68067e4314a0b55148e39e5d58a51b]
stable/5.4: [2f12258b5224cfaa808c54fd29345f3c1cbfca76]

CVE-2021-46952: NFS: fs_context: validate UDP retrans to prevent shift
out-of-bounds

Announce: https://lore.kernel.org/linux-cve-announce/20240227184057.2368370-17-gregkh@linuxfoundation.org/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Fix shift out-of-bounds in xprt_calc_majortimeo(). This is caused by a
garbage timeout (retrans) mount option being passed to nfs mount,
in this case from syzkaller.
If the protocol is XPRT_TRANSPORT_UDP, then 'retrans' is a shift value
for a 64-bit long integer, so 'retrans' cannot be >= 64.
If it is >= 64, fail the mount and return an error.

Introduced by commit 9954bf9 ("NFS: Move mount parameterisation bits
into their own file") in 5.6-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [c09f11ef35955785f92369e25819bf0629df2e59]
stable/5.10: [96fa26b74cdcf9f5c98996bf36bec9fb5b19ffe2]

CVE-2021-46953: ACPI: GTDT: Don't corrupt interrupt mappings on
watchdow probe failure

Announce: https://lore.kernel.org/linux-cve-announce/20240227184057.2368370-18-gregkh@linuxfoundation.org/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
ACPI: GTDT: Don't corrupt interrupt mappings on watchdow probe failure
When failing the driver probe because of invalid firmware properties,
the GTDT driver unmaps the interrupt that it mapped earlier. However,
it never checks whether the mapping of the interrupt actially
succeeded. Even more, should the firmware report an illegal interrupt
number
that overlaps with the GIC SGI range, this can result in an IPI being
unmapped, and subsequent fireworks (as reported by Dann Frazier).
Rework the driver to have a slightly saner behaviour and actually
check whether the interrupt has been mapped before unmapping things.

Introduced by commit ca9ae5e ("acpi/arm64: Add SBSA Generic Watchdog
support in GTDT driver") in 4.12-rc1.
This commit is not backported to 4.4.
Fixed in 5.13-rc1.

Fixed status
mainline: [1ecd5b129252249b9bc03d7645a7bda512747277]
stable/4.19: [7b2162db1498c71962a4bb2f776fa4e76d4d305b]
stable/5.10: [e0f2d86481eaa83df33b0793f75212919db7a19d]
stable/5.4: [504632a3577a049dd9bb7aabae5b4476f9c586b4]

CVE-2021-46954: net/sched: sch_frag: fix stack OOB read while
fragmenting IPv4 packets

Announce: https://lore.kernel.org/linux-cve-announce/2024022715-CVE-2021-46954-b856@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

A stack-out-of-bounds error in the Linux kernel's handling of IPv4
packet fragmentation, specifically when act_mirred attempts to
fragment
packets that have been reassembled using act_ct.

Introduced by commit c129412 ("net/sched: sch_frag: add generic packet
fragment support.") in 5.11-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [31fe34a0118e0acc958c802e830ad5d37ef6b1d3]

CVE-2021-46955: openvswitch: fix stack OOB read while fragmenting IPv4 packets

Announce: https://lore.kernel.org/linux-cve-announce/2024022718-CVE-2021-46955-b50b@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

When running Open vSwitch on kernels built with KASAN, testing IPv4
packet fragmentation reveals a stack-out-of-bounds bug in
ip_do_fragment.

Introduced by commit d52e5a7 ("ipv4: lock mtu in fnhe when received
PMTU < net.ipv4.route.min_pmt") in 4.16-rc7.
This commit is backported 4.4.
Fixed in 5.13-rc1.

Fixed status
cip/4.4: [b1d7280f9ba1bfdbc3af5bdb82e51f014854f26f]
cip/4.4-rt: [b1d7280f9ba1bfdbc3af5bdb82e51f014854f26f]
cip/4.4-st: [b1d7280f9ba1bfdbc3af5bdb82e51f014854f26f]
mainline: [7c0ea5930c1c211931819d83cfb157bff1539a4c]
stable/4.19: [df9e900de24637be41879e2c50afb713ec4e8b2e]
stable/5.10: [a1478374b0bda89b4277a8afd39208271faad4be]
stable/5.4: [490ad0a2390442d0a7b8c00972a83dbb09cab142]

CVE-2021-46956: virtiofs: fix memory leak in virtio_fs_probe()

Announce: https://lore.kernel.org/linux-cve-announce/2024022718-CVE-2021-46956-df60@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

When accidentally passing twice the same tag to qemu, kmemleak ended
up reporting a memory leak in virtiofs.

Introduced by commit a62a8ef ("virtio-fs: add virtiofs filesystem") in 5.4-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [c79c5e0178922a9e092ec8fed026750f39dcaef4]
stable/5.10: [d19555ff225d0896a33246a49279e6d578095f15]
stable/5.4: [310efc95c72c13faf855c692d19cd4d054d827c8]

CVE-2021-46957: riscv/kprobe: fix kernel panic when invoking sys_read
traced by kprobe

Announce: https://lore.kernel.org/linux-cve-announce/2024022718-CVE-2021-46957-90af@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Installing a kprobe at the entry of sys_read in kernels built with
KASAN can trigger a BUG_ON()
in __find_get_block, leading to a kernel bug report when testing IPv4
packet fragmentation.

Introduced by commit c22b0bc ("riscv: Add kprobes supported") in
5.12-rc1-dontuse.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [b1ebaa0e1318494a7637099a26add50509e37964]

CVE-2021-46958: btrfs: fix race between transaction aborts and fsyncs
leading to use-after-free

Announce: https://lore.kernel.org/linux-cve-announce/2024022718-CVE-2021-46958-53ff@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

There is a race between a task aborting a transaction during a commit,
a task doing an fsync and the transaction kthread, which leads to an
use-after-free of the log root tree.

Introduced by commit ef67963 ("btrfs: drop logs when we've aborted a
transaction") in 5.7-rc4.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [061dde8245356d8864d29e25207aa4daa0be4d3c]
stable/5.10: [a4794be7b00b7eda4b45fffd283ab7d76df7e5d6]

CVE-2021-46960: cifs: Return correct error code from smb2_get_enc_key

Announce: https://lore.kernel.org/linux-cve-announce/2024022718-CVE-2021-46960-f5ac@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Avoid a warning if the error percolates back up

Introduced by commit 61cfac6 ("CIFS: Fix possible use after free in
demultiplex thread") in 4.11-rc1.
This commit is not backported to 4.4.
Fixed in 5.13-rc1.

Fixed status
mainline: [83728cbf366e334301091d5b808add468ab46b27]
stable/4.19: [e486f8397f3f14a7cadc166138141fdb14379a54]
stable/5.10: [aaa0faa5c28a91c362352d6b35dc3ed10df56fb0]
stable/5.4: [93f3339b22ba17e66f0808737467b70ba087eaec]

CVE-2021-46961: irqchip/gic-v3: Do not enable irqs when handling
spurious interrups

Announce: https://lore.kernel.org/linux-cve-announce/2024022719-CVE-2021-46961-6212@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Running a 4.19 kernel with backported pseudo-NMI patches, a BUG_ON()
error was triggered due to spurious interrupts causing nested
Non-Maskable Interrupts (NMIs), which are unmanageable.

Introduced by commit 3f1f323 ("irqchip/gic-v3: Switch to PMR masking
before calling IRQ handler") in 5.1-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [a97709f563a078e259bf0861cd259aa60332890a]
stable/5.10: [7be4db5c2b59fa77071c93ca4329876fb9777202]
stable/5.4: [e7ea8e46e3b777be26aa855fe07778c415f24926]

CVE-2021-46962: mmc: uniphier-sd: Fix a resource leak in the remove function

Announce: https://lore.kernel.org/linux-cve-announce/2024022719-CVE-2021-46962-e081@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
mmc: uniphier-sd: Fix a resource leak in the remove function A
'tmio_mmc_host_free()'
call is missing in the remove function, in order to balance a
'tmio_mmc_host_alloc()' call in the probe. This is done in the error
handling path of
the probe, but not in the remove function. Add the missing call.

Introduced by commit 3fd784f ("mmc: uniphier-sd: add UniPhier SD/eMMC
controller driver") in 4.20-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [e29c84857e2d51aa017ce04284b962742fb97d9e]
stable/5.10: [25ac6ce65f1ab458982d15ec1caf441acd37106a]
stable/5.4: [0d8941b9b2d3e7b3481fdf43b1a6189d162175b7]

CVE-2021-46963: scsi: qla2xxx: Fix crash in qla2xxx_mqueuecommand()

Announce: https://lore.kernel.org/linux-cve-announce/2024022719-CVE-2021-46963-32a8@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Fix incorrect call to free srb in qla2xxx_mqueuecommand(), as srb is
now allocated by upper layers. This fixes smatch warning of srb
unintended free.

Introduced by commit af2a0c5 ("scsi: qla2xxx: Fix SRB leak on switch
command timeout") in 5.5-rc1.
This commit is backported to 4.19 and 5.4. Linux 4.4 is not affected.
Fixed in 5.13-rc1.

Fixed status
mainline: [6641df81ab799f28a5d564f860233dd26cca0d93]
stable/4.19: [c5ab9b67d8b061de74e2ca51bf787ee599bd7f89]
stable/5.10: [702cdaa2c6283c135ef16d52e0e4e3c1005aa538]
stable/5.4: [77509a238547863040a42d57c72403f7d4c89a8f]

CVE-2021-46964: scsi: qla2xxx: Reserve extra IRQ vectors

Announce: https://lore.kernel.org/linux-cve-announce/2024022719-CVE-2021-46964-da8c@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

The commit a6dcfe0 to the qla2xxx SCSI driver limits MSI-X vector
allocation to the CPU count, disrupting assumptions in several
functions and
setting max_qpairs to zero for two CPUs in initiator mode. This
results in ha->queue_pair_map being NULL, causing a crash in
qla2xxx_queuecommand() due to a NULL pointer dereference when the
driver attempts to access queue pairs that it believes are available.

Introduced by commit a6dcfe0 ("scsi: qla2xxx: Limit interrupt vectors
to number of CPUs") in 5.11-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [f02d4086a8f36a0e1aaebf559b54cf24a177a486]

CVE-2021-46965: mtd: physmap: physmap-bt1-rom: Fix unintentional stack access

Announce: https://lore.kernel.org/linux-cve-announce/2024022719-CVE-2021-46965-3b74@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
mtd: physmap: physmap-bt1-rom: Fix unintentional stack access Cast
&data
to (char *) in order to avoid unintentionally accessing the stack.
Notice that data is of type u32, so any increment to &data will be in
the order of 4-byte chunks, and this piece of code is actually
intended to be a byte offset. Addresses-Coverity-ID: 1497765
("Out-of-bounds access")

Introduced by commit b3e79e7 ("mtd: physmap: Add Baikal-T1 physically
mapped ROM support") in 5.10-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [683313993dbe1651c7aa00bb42a041d70e914925]
stable/5.10: [34ec706bf0b7c4ca249a729c1bcb91f706c7a7be]

CVE-2021-46966: ACPI: custom_method: fix potential use-after-free issue

In the Linux kernel, the following vulnerability has been resolved:
ACPI: custom_method: fix potential use-after-free issue In cm_write(),
buf is always freed when reaching the end of the function. If the
requested count is less than table.length, the allocated buffer will
be
freed but subsequent calls to cm_write() will still try to access it.
Remove the unconditional kfree(buf) at the end of the function and set
the buf to NULL in the -EINVAL error path to match the rest of function.

Introduced by commit 03d1571 ("ACPI: custom_method: fix memory leaks")
in 5.4-rc1.
This commit is backported to 4.19 and 4.4.
Fixed in 5.13-rc1.

Fixed status
cip/4.4: [1d53ca5d131074c925ce38361fb0376d3bf7e394]
cip/4.4-rt: [1d53ca5d131074c925ce38361fb0376d3bf7e394]
cip/4.4-st: [1d53ca5d131074c925ce38361fb0376d3bf7e394]
mainline: [e483bb9a991bdae29a0caa4b3a6d002c968f94aa]
stable/4.19: [a5b26a2e362f572d87e9fd35435680e557052a17]
stable/5.10: [62dc2440ebb552aa0d7f635e1697e077d9d21203]
stable/5.4: [72814a94c38a33239793f7622cec6ace1e540c4b]

CVE-2021-46967: vhost-vdpa: fix vm_flags for virtqueue doorbell mapping

Announce: https://lore.kernel.org/linux-cve-announce/2024022720-CVE-2021-46967-c991@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
vhost-vdpa: fix vm_flags for virtqueue doorbell mapping
The virtqueue doorbell is usually implemented via registeres but we
don't provide the necessary vma->flags like VM_PFNMAP. This may
cause several issues e.g when userspace tries to map the doorbell via
vhost IOTLB, kernel may panic due to the page is not backed
by page structure. This patch fixes this by setting the necessary
vm_flags. With this patch, try to map doorbell via IOTLB will
fail with bad address.

Introduced by commit ddd89d0 ("vhost_vdpa: support doorbell mapping
via mmap") in 5.8-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [3a3e0fad16d40a2aa68ddf7eea4acdf48b22dd44]
stable/5.10: [3b8b6399666a29daa30b0bb3f5c9e3fc81c5a6a6]

CVE-2021-46968: s390/zcrypt: fix zcard and zqueue hot-unplug memleak

Announce: https://lore.kernel.org/linux-cve-announce/2024022720-CVE-2021-46968-8c71@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Tests with kvm and a kmemdebug kernel showed, that on hot unplug the
zcard and zqueue structs for the unplugged card or queue are not
properly freed because of a mismatch with get/put for the embedded kref counter.
This fix now adjusts the handling of the kref counters. With init the
kref counter starts with 1. This initial value needs to drop to zero
with the unregister of the card or queue to trigger the release and
free the object.

Introduced by commit 29c2680 ("s390/ap: fix ap devices reference
counting") in 5.10-rc3.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [70fac8088cfad9f3b379c9082832b4d7532c16c2]
stable/5.10: [026499a9c2e002e621ad568d1378324ae97e5524]

CVE-2021-46970: bus: mhi: pci_generic: Remove WQ_MEM_RECLAIM flag from
state workqueue

Announce: https://lore.kernel.org/linux-cve-announce/2024022720-CVE-2021-46970-de08@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

A recent change created a dedicated workqueue for the state-change
work with WQ_HIGHPRI (no strong reason for that) and WQ_MEM_RECLAIM
flags,
but the state-change work (mhi_pm_st_worker) does not guarantee
forward progress under memory pressure, and will even wait on various
memory
allocations when e.g. creating devices, loading firmware, etc... The
work is then not part of a memory reclaim path...
Moreover, this causes a warning in check_flush_dependency() since we
end up in code that flushes a non-reclaim workqueue:

Introduced by commit 8f70397 ("bus: mhi: core: Move to using high
priority workqueue") in 5.11-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [0fccbf0a3b690b162f53b13ed8bc442ea33437dc]

CVE-2021-46971: perf/core: Fix unconditional security_locked_down() call

Announce: https://lore.kernel.org/linux-cve-announce/2024022721-CVE-2021-46971-9534@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
perf/core: Fix unconditional security_locked_down() call Currently,
the lockdown state is queried unconditionally, even though its result
is used only if the PERF_SAMPLE_REGS_INTR bit is set in
attr.sample_type.
While that doesn't matter in case of the Lockdown LSM, it causes
trouble with the SELinux's lockdown hook implementation. SELinux
implements
the locked_down hook with a check whether the current task's type has
the corresponding "lockdown" class permission ("integrity" or
"confidentiality")
allowed in the policy. This means that calling the hook when the
access control decision would be ignored generates a bogus permission
check and audit
 record. Fix this by checking sample_type first and only calling the
hook when its result would be honored.

Introduced by commit b0c8fdc ("lockdown: Lock down perf when in
confidentiality mode") in 5.4-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [08ef1af4de5fe7de9c6d69f1e22e51b66e385d9b]
stable/5.10: [4348d3b5027bc3ff6336368b6c60605d4ef8e1ce]
stable/5.4: [b246759284d6a2bc5b6f1009caeeb3abce2ec9ff]

CVE-2021-46974: bpf: Fix masking negation logic upon negative dst register

Announce: https://lore.kernel.org/linux-cve-announce/2024022721-CVE-2021-46974-0852@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
bpf: Fix masking negation logic upon negative dst register The
negation
logic for the case where the off_reg is sitting in the dst register is
not correct given then we cannot just invert the add to a sub or vice
versa. As a fix, perform the final bitwise and-op unconditionally into
AX from the off_reg, then move the pointer from the src to dst and
finally use AX as the source for the original pointer arithmetic
operation such that the inversion yields a correct result. The single
non-AX mov in between is possible given constant blinding is retaining
it as it's not an immediate based operation.

Introduced by commit 979d63d ("bpf: prevent out of bounds speculation
on pointer arithmetic") in 5.0-rc1.
This commit is backported to 4.19. Linux 4.4 is not affected.
Fixed in 5.13-rc1.

Fixed status
mainline: [b9b34ddbe2076ade359cd5ce7537d5ed019e9807]
stable/4.19: [0e2dfdc74a7f4036127356d42ea59388f153f42c]
stable/5.10: [2cfa537674cd1051a3b8111536d77d0558f33d5d]
stable/5.4: [53e0db429b37a32b8fc706d0d90eb4583ad13848]

CVE-2021-46975: netfilter: conntrack: Make global sysctls readonly in
non-init netns

Announce: https://lore.kernel.org/linux-cve-announce/2024022721-CVE-2021-46975-248d@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
netfilter: conntrack: Make global sysctls readonly in non-init netns
These sysctls point to global variables: - NF_SYSCTL_CT_MAX
(&nf_conntrack_max) - NF_SYSCTL_CT_EXPECT_MAX (&nf_ct_expect_max) -
NF_SYSCTL_CT_BUCKETS (&nf_conntrack_htable_size_user) Because their
data pointers are not updated to point to per-netns structures,
they must be marked read-only in a non-init_net ns. Otherwise, changes
in any net namespace are reflected in (leaked into) all other net
namespaces. This problem has existed since the introduction of net
namespaces. The current logic marks them read-only only if the net
namespace
is owned by an unprivileged user (other than init_user_ns). Commit
d0febd81ae77 ("netfilter: conntrack: re-visit sysctls in unprivileged
namespaces") "exposes all sysctls even if the namespace is
unpriviliged." Since we need to mark them readonly in any case, we can
forego the
unprivileged user check altogether.

Introduced by commit d0febd8 ("netfilter: conntrack: re-visit sysctls
in unprivileged namespaces") in 5.7-rc1.
Linux 4.4 is not affected.
Fixed in 5.13-rc1.

Fixed status
mainline: [2671fa4dc0109d3fb581bc3078fdf17b5d9080f6]
stable/4.19: [9b288479f7a901a14ce703938596438559d7df55]
stable/5.10: [d3598eb3915cc0c0d8cab42f4a6258ff44c4033e]
stable/5.4: [baea536cf51f8180ab993e374cb134b5edad25e2]

CVE-2021-46907: KVM: VMX: Don't use vcpu->run->internal.ndata as an array index

Announce: https://lore.kernel.org/linux-cve-announce/2024022703-CVE-2021-46907-85de@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
KVM: VMX: Don't use vcpu->run->internal.ndata as an array index
__vmx_handle_exit() uses vcpu->run->internal.ndata as an index for an
array access. Since vcpu->run is (can be) mapped to a user address
space with a writer permission, the 'ndata' could be updated by the
user process at anytime (the user process can set it to outside the
bounds of the array). So, it is not safe that __vmx_handle_exit() uses
the 'ndata' that way.

Introcued by commit 1aa561b ("kvm: x86: Add "last CPU" to some
KVM_EXIT information") in 5.9-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.12-rc8.

Fixed status
mainline: [04c4f2ee3f68c9a4bf1653d15f1a9a435ae33f7a]
stable/5.10: [7f64753835a78c7d2cc2932a5808ef3b7fd4c050]

CVE-2021-46908: bpf: Use correct permission flag for mixed signed
bounds arithmetic

Announce: https://lore.kernel.org/linux-cve-announce/2024022706-CVE-2021-46908-5030@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

We forbid adding unknown scalars with mixed signed bounds due to the
spectre v1 masking mitigation. Hence this also needs bypass_spec_v1
flag instead of allow_ptr_leaks.

Introduced by commit 2c78ee8 ("bpf: Implement CAP_BPF") in 5.8-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.12-rc8.

Fixed status
mainline: [9601148392520e2e134936e76788fc2a6371e7be]
stable/5.10: [4f3ff11204eac0ee23acf64deecb3bad7b0db0c6]

CVE-2021-46909: ARM: footbridge: fix PCI interrupt mapping

Announce: https://lore.kernel.org/linux-cve-announce/2024022707-CVE-2021-46909-8fb6@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
ARM: footbridge: fix PCI interrupt mapping Since commit
30fdfb929e82 ("PCI: Add a call to pci_assign_irq() in
pci_device_probe()"), the PCI code will call the IRQ mapping function
whenever
a PCI driver is probed. If these are marked as __init, this causes an
oops if a PCI driver is loaded or bound after the kernel has
initialised.

Introduced by commit 30fdfb9 ("PCI: Add a call to pci_assign_irq() in
pci_device_probe()") in 4.13-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.12-rc8.

Fixed status
mainline: [30e3b4f256b4e366a61658c294f6a21b8626dda7]
stable/4.19: [2643da6aa57920d9159a1a579fb04f89a2b0d29a]
stable/5.10: [1fc087fdb98d556b416c82ed6e3964a30885f47a]
stable/5.4: [871b569a3e67f570df9f5ba195444dc7c621293b]

CVE-2021-46911: ch_ktls: Fix kernel panic

Announce: https://lore.kernel.org/linux-cve-announce/2024022708-CVE-2021-46911-2a14@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
ch_ktls: Fix kernel panic Taking page refcount is not ideal and causes
 kernel panic sometimes. It's better to take tx_ctx lock for the
complete skb transmit, to avoid page cleanup if ACK received in
middle.

Introduced by commit 5a4b9fe ("cxgb4/chcr: complete record tx
handling") in 5.7-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.12-rc8.

mainline: [1a73e427b824133940c2dd95ebe26b6dce1cbf10]
stable/5.10: [8d5a9dbd2116a852f8f0f91f6fbc42a0afe1091f]

CVE-2021-46912: net: Make tcp_allowed_congestion_control readonly in
non-init netns

Announce: https://lore.kernel.org/linux-cve-announce/2024022708-CVE-2021-46912-d07b@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
net: Make tcp_allowed_congestion_control readonly in non-init netns
Currently,
tcp_allowed_congestion_control is global and writable; writing to it
in any net namespace will leak into all other net namespaces.
tcp_available_congestion_control and tcp_allowed_congestion_control
are the only sysctls in ipv4_net_table (the per-netns sysctl table)
with
a NULL data pointer; their handlers
(proc_tcp_available_congestion_control and
proc_allowed_congestion_control) have no other way of referencing
a struct net. Thus, they operate globally. Because ipv4_net_table does
not use designated initializers, there is no easy way to fix up this
one
"bad" table entry. However, the data pointer updating logic shouldn't
be applied to NULL pointers anyway, so we instead force these entries
to be
read-only. These sysctls used to exist in ipv4_table (init-net only),
but they were moved to the per-net ipv4_net_table, presumably without
realizing that tcp_allowed_congestion_control was writable and thus
introduced a leak. Because the intent of that commit was only to know
(i.e. read)
"which congestion algorithms are available or allowed", this read-only
solution should be sufficient. The logic added in recent commit
31c4d2f160eb: ("net: Ensure net namespace isolation of sysctls") does
not and cannot check for NULL data pointers, because other table
entries (e.g. /proc/sys/net/netfilter/nf_log/) have .data=NULL but use
other methods (.extra2) to access the struct net.

Introduced by commit 31c4d2f: ("net: Ensure net namespace isolation of
sysctls") in 5.7-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.12-rc8.

Fixed status
mainline: [97684f0970f6e112926de631fdd98d9693c7e5c1]
stable/5.10: [35d7491e2f77ce480097cabcaf93ed409e916e12]

CVE-2021-46910: ARM: 9063/1: mm: reduce maximum number of CPUs if
DEBUG_KMAP_LOCAL is enabled

Announce: https://lore.kernel.org/linux-cve-announce/2024022707-CVE-2021-46910-ba92@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

The debugging code for kmap_local() doubles the number of per-CPU
fixmap slots allocated for kmap_local(), in order to use half of them
as guard
regions. This causes the fixmap region to grow downwards beyond the
start of its reserved window if the supported number of CPUs is large,
and collide
with the newly added virtual DT mapping right below it, which is
obviously not good.

Introduced by commit 2a15ba8 ("ARM: highmem: Switch to generic kmap
atomic") in 5.11-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.12-rc8.

Fixed status
mainline: [d624833f5984d484c5e3196f34b926f9e71dafee]

CVE-2021-46914: ixgbe: fix unbalanced device enable/disable in suspend/resume

Announce: ixgbe: fix unbalanced device enable/disable in suspend/resume
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

pci_disable_device() called in __ixgbe_shutdown() decreases
dev->enable_cnt by 1. pci_enable_device_mem() which increases
dev->enable_cnt by 1, was removed from ixgbe_resume() in commit
6f82b2558735 ("ixgbe: use generic power management"). This caused
unbalanced increase/decrease. So add pci_enable_device_mem() back.

Introdcued by commit 6f82b25 ("ixgbe: use generic power management") in 5.9-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.12-rc8.

Fixed status
mainline: [debb9df311582c83fe369baa35fa4b92e8a9c58a]
stable/5.10: [be07581aacae7cd0a073afae8e8862032f794309]

CVE-2021-46915: netfilter: nft_limit: avoid possible divide error in
nft_limit_init

Announce: https://lore.kernel.org/linux-cve-announce/2024022709-CVE-2021-46915-7ded@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

nft_limit_init() wants to divide u64 by u64, use the appropriate math
function (div64_u64).

Introduced by commit c26844e ("netfilter: nf_tables: Fix nft limit
burst handling") in 4.13 and
3e0f64b ("netfilter: nft_limit: fix packet ratelimiting") in 4.17.
Linux 4.4 is not affected.
Fixed in 5.12-rc8.

Fixed status
mainline: [b895bdf5d643b6feb7c60856326dd4feb6981560]
stable/4.19: [fadd3c4afdf3d4c21f4d138502f8b76334987e26]
stable/5.10: [dc1732baa9da5b68621586bf8636ebbc27dc62d2]
stable/5.4: [01fb1626b620cb37a65ad08e0f626489e8f042ef]

CVE-2021-46913: netfilter: nftables: clone set element expression template

Announce: https://lore.kernel.org/linux-cve-announce/2024022708-CVE-2021-46913-eeef@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

memcpy() breaks when using connlimit in set elements. Use
nft_expr_clone() to initialize the connlimit expression list,
otherwise
connlimit garbage collector crashes when walking on the list head copy.

Introduced by commit 4094445 ("netfilter: nf_tables: add elements with
stateful expressions") in 5.7-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.12-rc8.

Fixed status
mainline: [4d8f9065830e526c83199186c5f56a6514f457d2]
stable/5.10: [e51ff3ffc316377cca21de8b80404eed0c37b3c3]

CVE-2021-46917: dmaengine: idxd: fix wq cleanup of WQCFG registers

Announce: https://lore.kernel.org/linux-cve-announce/2024022710-CVE-2021-46917-99a4@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

A pre-release silicon erratum workaround where wq reset does not clear
WQCFG registers was leaked into upstream code. Use wq reset command
instead of blasting the MMIO region. This also address an issue where
we clobber registers in future devices.

Introduced by commit da32b28 ("dmaengine: idxd: cleanup workqueue
config after disabling") in 5.8-rc6.
This commit is not backported to older stable kernels.
Fixed in 5.12-rc8.

Fixed status
mainline: [ea9aadc06a9f10ad20a90edc0a484f1147d88a7a]
stable/5.10: [e5eb9757fe4c2392e069246ae78badc573af1833]

CVE-2021-46918: dmaengine: idxd: clear MSIX permission entry on shutdown

Announce: https://lore.kernel.org/linux-cve-announce/2024022710-CVE-2021-46918-1dd0@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Add disabling/clearing of MSIX permission entries on device shutdown
to mirror the enabling of the MSIX entries on probe. Current code left
the
MSIX enabled and the pasid entries still programmed at device shutdown.

Introduced by commit 8e50d39 ("dmaengine: idxd: Add shared workqueue
support") in 5.11-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.12-rc8.

Fixed status
mainline: [6df0e6c57dfc064af330071f372f11aa8c584997]

CVE-2021-46916: ixgbe: Fix NULL pointer dereference in ethtool loopback test

Announce: https://lore.kernel.org/linux-cve-announce/2024022709-CVE-2021-46916-9f19@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

The ixgbe driver currently generates a NULL pointer dereference when
performing the ethtool loopback test. This is due to the fact that
there
isn't a q_vector associated with the test ring when it is setup as
interrupts are not normally added to the test rings.
To address this I have added code that will check for a q_vector
before returning a napi_id value. If a q_vector is not present it will
return a
value of 0.

Introduced by commit b02e5a0 ("xsk: Propagate napi_id to XDP socket Rx
path") in 5.11-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.12-rc8.

Fixed status
mainline: [31166efb1cee348eb6314e9c0095d84cbeb66b9d]

CVE-2021-46920: dmaengine: idxd: Fix clobbering of SWERR overflow bit
on writeback

Announce: https://lore.kernel.org/linux-cve-announce/2024022711-CVE-2021-46920-062e@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Current code blindly writes over the SWERR and the OVERFLOW bits.
Write back the bits actually read instead so the driver avoids
clobbering the
OVERFLOW bit that comes after the register is read.

Introduced by commit bfe1d56 ("dmaengine: idxd: Init and probe for
Intel data accelerators") in 5.6-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.12-rc8.

Fixed status
mainline: [ea941ac294d75d0ace50797aebf0056f6f8f7a7f]
stable/5.10: [a5ad12d5d69c63af289a37f05187a0c6fe93553d]

CVE-2021-46919: dmaengine: idxd: fix wq size store permission state

Announce: https://lore.kernel.org/linux-cve-announce/2024022710-CVE-2021-46919-950c@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

WQ size can only be changed when the device is disabled. Current code
allows change when device is enabled but wq is disabled. Change the
check
to detect device state.

Introduced by commit c52ca47 ("dmaengine: idxd: add configuration
component of driver") in 5.6-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.12-rc8.

Fixed status
mainline: [0fff71c5a311e1264988179f7dcc217fda15fadd]
stable/5.10: [4ecf25595273203010bc8318c4aee60ad64037ae]

CVE-2021-46921: dmaengine: idxd: add configuration component of driver

Announce: https://lore.kernel.org/linux-cve-announce/2024022732-CVE-2021-46921-91dc@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

A concurrency issue in epoll was identified where a writer, while
holding the wait_lock, checks a value using atomic_cond_read_acquire()
but only acquires the lock upon a successful compare-and-exchange
(cmpxchg) operation, which isn't ordered. This creates a vulnerability
to an A-B-A problem, allowing readers to observe speculative values
before the write lock is fully secured.

Introduced by commit b519b56 ("locking/qrwlock: Use
atomic_cond_read_acquire() when spinning in qrwlock") in 4.15-rc1.
Linux 4.4 is not affected.
Fixed in 5.12.

Fixed status
mainline: [84a24bf8c52e66b7ac89ada5e3cfbe72d65c1896]
stable/4.19: [5902f9453a313be8fe78cbd7e7ca9dba9319fc6e]
stable/5.10: [82fa9ced35d88581cffa4a1c856fc41fca96d80a]
stable/5.4: [82808cc026811fbc3ecf0c0b267a12a339eead56]

CVE-2021-46922: KEYS: trusted: Fix TPM reservation for seal/unseal

Announce: https://lore.kernel.org/linux-cve-announce/2024022736-CVE-2021-46922-39b5@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

This is backport issue. Backporting commit 67118bb ("KEYS: trusted:
Reserve TPM for seal and unseal operations") to 5.10 introduced this
issue.

Fixed status
stable/5.10: [bf84ef2dd2ccdcd8f2658476d34b51455f970ce4]

CVE-2021-46924: NFC: st21nfca: Fix memory leak in device probe and remove

Announce: https://lore.kernel.org/linux-cve-announce/2024022748-CVE-2021-46924-3483@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

'phy->pending_skb' is alloced when device probe, but forgot to free in
the error handling path and remove path, this cause memory leak.

Introduced by commit 6895730 ("NFC: ST21NFCA: Add driver for
STMicroelectronics ST21NFCA NFC Chip") in 3.16-rc1.
Fixed in 5.16-rc8.

Fixed status
mainline: [1b9dadba502234eea7244879b8d5d126bfaf9f0c]
stable/4.19: [a1e0080a35a16ce3808f7040fe0c3a8fdb052349]
stable/5.10: [e553265ea56482da5700f56319fda9ff53e7dcb4]
stable/5.15: [238920381b8925d070d32d73cd9ce52ab29896fe]
stable/5.4: [1cd4063dbc91cf7965d73a6a3855e2028cd4613b]

CVE-2021-46933: usb: gadget: f_fs: Clear ffs_eventfd in ffs_data_clear

Announce: https://lore.kernel.org/linux-cve-announce/2024022750-CVE-2021-46933-2103@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

ffs_data_clear is indirectly called from both ffs_fs_kill_sb and
ffs_ep0_release, so it ends up being called twice when userland closes
ep0
and then unmounts f_fs.  If userland provided an eventfd along with
function's USB descriptors, it
ends up calling eventfd_ctx_put as many times, causing a refcount underflow.
NULL-ify ffs_eventfd to prevent these extraneous eventfd_ctx_put
calls. Also, set epfiles to NULL right after de-allocating it, for
readability.
For completeness, ffs_data_clear actually ends up being called thrice,
the last call being before the whole ffs structure gets freed, so when
this
specific sequence happens there is a second underflow happening (but
not being reported):

Introduced by commit 5e33f6f ("usb: gadget: ffs: add eventfd
notification about ffs events") in 4.0-rc1.
Fixed in 5.16-rc8.

Fixed status
cip/4.4: [f976dd7011150244a7ba820f2c331e9fb253befa]
cip/4.4-rt: [f976dd7011150244a7ba820f2c331e9fb253befa]
cip/4.4-st: [f976dd7011150244a7ba820f2c331e9fb253befa]
mainline: [b1e0887379422975f237d43d8839b751a6bcf154]
stable/4.19: [33f6a0cbb7772146e1c11f38028fffbfed14728b]
stable/5.10: [1c4ace3e6b8575745c50dca9e76e0021e697d645]
stable/5.15: [ebef2aa29f370b5096c16020c104e393192ef684]
stable/5.4: [240fc586e83d645912accce081a48aa63a45f6ee]

CVE-2021-46934: i2c: validate user data in compat ioctl

Announce: https://lore.kernel.org/linux-cve-announce/2024022750-CVE-2021-46934-79c8@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Wrong user data may cause warning in i2c_transfer(), ex: zero msgs.
Userspace should not be able to trigger warnings, so this patch adds
validation checks for user data in compact ioctl to prevent reported warnings

Introduced by commit 7d5cb45 ("i2c compat ioctls: move to
->compat_ioctl()") in 4.15-rc1.
Linux 4.4 is not affected.
Fixed in 5.16-rc8.

Fixed status
mainline: [bb436283e25aaf1533ce061605d23a9564447bdf]
stable/4.19: [407c8708fb1bf2d4afc5337ef50635cf540c364b]
stable/5.10: [8d31cbab4c295d7010ebb729e9d02d0e9cece18f]
stable/5.15: [f68599581067e8a5a8901ba9eb270b4519690e26]
stable/5.4: [9e4a3f47eff476097e0c7faac04d1831fc70237d]

CVE-2021-46935: binder: fix async_free_space accounting for empty parcels

Announce: https://lore.kernel.org/linux-cve-announce/2024022751-CVE-2021-46935-f8f4@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
binder: fix async_free_space accounting for empty parcels In 4.13,
commit 74310e06be4d ("android: binder: Move buffer out of area shared
with user space") fixed a kernel structure visibility issue.
As part of that patch, sizeof(void *) was used as the buffer size for
0-length data payloads so the driver could detect abusive clients
sending 0-length asynchronous transactions to a server by enforcing
limits on async_free_size. Unfortunately, on the "free" side,
the accounting of async_free_space did not add the sizeof(void *)
back. The result was that up to 8-bytes of async_free_space were
leaked on every async transaction of 8-bytes or less. These small
transactions are uncommon, so this accounting issue has gone
undetected
for several years. The fix is to use "buffer_size" (the allocated
buffer size) instead of "size" (the logical buffer size) when updating
the async_free_space during the free operation. These are the same
except for this corner case of asynchronous transactions with payloads
< 8 bytes.

Introduced by commit 74310e0 ("android: binder: Move buffer out of
area shared with user space") in 4.14-rc1.
Linux 4.4 is not affected.
Fixed in 5.16-rc8.

Fixed status
mainline: [cfd0d84ba28c18b531648c9d4a35ecca89ad9901]
stable/4.19: [7c7064402609aeb6fb11be1b4ec10673ff17b593]
stable/5.10: [1cb8444f3114f0bb2f6e3bcadcf09aa4a28425d4]
stable/5.15: [17691bada6b2f1d5f1c0f6d28cd9d0727023b0ff]
stable/5.4: [103b16a8c51f96d5fe063022869ea906c256e5da]

CVE-2021-46936: net: fix use-after-free in tw_timer_handler

Announce: https://lore.kernel.org/linux-cve-announce/2024022751-CVE-2021-46936-2f8a@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

A panic issue in Linux 5.4 related to a page fault in tw_timer_handler
was reported, persisting despite DCCP fixes. The problem originates
from ipv4_mib_exit_net being called before tcp_sk_exit_batch due to
the order of operations in the destruction of a net namespace,
leading to a use-after-free error. This issue, introduced by a change
that allocated net statistics to struct net, was fixed by adjusting
the initialization order of IPv4 MIBs relative to TCP and changing a
critical error reporting to a panic for failure in init_ipv4_mibs.

Introduced by commit 61a7e26 ("mib: put net statistics on struct net")
in 2.6.27-rc1.
Fixed in 5.16-rc8.

Fixed status
cip/4.4: [15579e1301f856ad9385d720c9267c11032a5022]
cip/4.4-rt: [15579e1301f856ad9385d720c9267c11032a5022]
cip/4.4-st: [15579e1301f856ad9385d720c9267c11032a5022]
mainline: [e22e45fc9e41bf9fcc1e92cfb78eb92786728ef0]
stable/4.19: [a8e1944b44f94f5c5f530e434c5eaee787254566]
stable/5.10: [2386e81a1d277f540e1285565c9d41d531bb69d4]
stable/5.15: [08eacbd141e2495d2fcdde84358a06c4f95cbb13]
stable/5.4: [fe5838c22b986c1190f1dce9aa09bf6a491c1a69]

CVE-2021-46937: mm/damon/dbgfs: fix 'struct pid' leaks in
'dbgfs_target_ids_write()'

Announce: https://lore.kernel.org/linux-cve-announce/2024022751-CVE-2021-46937-3ae8@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

DAMON debugfs interface increases the reference counts of 'struct
pid's for targets from the 'target_ids' file write callback
('dbgfs_target_ids_write()'), but decreases the counts only in DAMON
monitoring termination callback ('dbgfs_before_terminate()').
Therefore, when 'target_ids' file is repeatedly written without DAMON
monitoring start/termination, the reference count is not decreased and
therefore memory for the 'struct pid' cannot be freed.  This commit
fixes this issue by decreasing the reference counts when 'target_ids'
is
written.

Introduced by commit 4bc0595 ("mm/damon: implement a debugfs-based
user space interface") in 5.15-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.16-rc8.

Fixed status
mainline: [ebb3f994dd92f8fb4d70c7541091216c1e10cb71]
stable/5.15: [ffe4a1ba1a82c416a6b3a09d46594f6a885ae141]

CVE-2021-46927: nitro_enclaves: Use get_user_pages_unlocked() call to
handle mmap assert

Announce: https://lore.kernel.org/linux-cve-announce/2024022749-CVE-2021-46927-ae70@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

After commit 5b78ed24e8ec ("mm/pagemap: add mmap_assert_locked()
annotations to find_vma*()"), the call to get_user_pages() will
trigger
the mmap assert.

Introduced by commit 5b78ed2 ("mm/pagemap: add mmap_assert_locked()
annotations to find_vma*()") in 5.15-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.16-rc8.

Fixed status
mainline: [3a0152b219523227c2a62a0a122cf99608287176]
stable/5.15: [90d2beed5e753805c5eab656b8d48257638fe543]

CVE-2021-46929: sctp: use call_rcu to free endpoint

Announce: https://lore.kernel.org/linux-cve-announce/2024022749-CVE-2021-46929-9369@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

This patch is to delay the endpoint free by calling call_rcu() to fix
another use-after-free issue in sctp_sock_dump().

Introduced by commit d25adbe ("sctp: fix an use-after-free issue in
sctp_sock_dump") in 4.14-rc1.
Linux 4.4 is not affected.
Fixed in 5.16-rc8.

Fixed status
mainline: [5ec7d18d1813a5bead0b495045606c93873aecbb]
stable/4.19: [af6e6e58f7ebf86b4e7201694b1e4f3a62cbc3ec]
stable/5.10: [769d14abd35e0e153b5149c3e1e989a9d719e3ff]
stable/5.15: [75799e71df1da11394740b43ae5686646179561d]
stable/5.4: [831de271452b87657fcf8d715ee20519b79caef5]

CVE-2021-46930: usb: mtu3: fix list_head check warning

Announce: https://lore.kernel.org/linux-cve-announce/2024022749-CVE-2021-46930-99ca@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

This is caused by uninitialization of list_head.
BUG: KASAN: use-after-free in __list_del_entry_valid+0x34/0xe4

Introduced by commit 83374e0 ("usb: mtu3: add tracepoints to help
debug") in 5.2-rc1.
Linux 4.4 is not affected.
Fixed in 5.16-rc8.

Fixed status
mainline: [8c313e3bfd9adae8d5c4ba1cc696dcbc86fbf9bf]
stable/5.10: [3b6efe0b7ba03cc2acf0694b46d6ff33c5b4c295]
stable/5.15: [249ddfbe00570d6dc76208e88017937d4d374c79]
stable/5.4: [585e2b244dda7ea733274e4b8fa27853d625d3bf]

CVE-2021-46931: net/mlx5e: Wrap the tx reporter dump callback to extract the sq

Announce: https://lore.kernel.org/linux-cve-announce/2024022750-CVE-2021-46931-a468@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Function mlx5e_tx_reporter_dump_sq() casts its void * argument to
struct mlx5e_txqsq *, but in TX-timeout-recovery flow the argument is
actually
of type struct mlx5e_tx_timeout_ctx *.

Introduced by commit 5f29458 ("net/mlx5e: Support dump callback in TX
reporter") in 5.7-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.16-rc8.

Fixed status
mainline: [918fc3855a6507a200e9cf22c20be852c0982687]
stable/5.10: [73665165b64a8f3c5b3534009a69be55bb744f05]
stable/5.15: [07f13d58a8ecc3baf9a488588fb38c5cb0db484f]

CVE-2021-46932: Input: appletouch - initialize work before device registration

Announce: https://lore.kernel.org/linux-cve-announce/2024022750-CVE-2021-46932-3a36@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Syzbot has reported warning in __flush_work(). This warning is caused
by work->func == NULL, which means missing work initialization.
This may happen, since input_dev->close() calls
cancel_work_sync(&dev->work), but dev->work initalization happens
_after_
input_register_device() call.  So this patch moves dev->work
initialization before registering input device.

Introduced by commit 5a6eb67 ("Input: appletouch - improve powersaving
for Geyser3 devices") in 2.6.23-rc1.
Fixed in 5.16-rc8.

Fixed status
cip/4.4: [d2cb2bf39a6d17ef4bdc0e59c1a35cf5751ad8f4]
cip/4.4-rt: [d2cb2bf39a6d17ef4bdc0e59c1a35cf5751ad8f4]
cip/4.4-st: [d2cb2bf39a6d17ef4bdc0e59c1a35cf5751ad8f4]
mainline: [9f3ccdc3f6ef10084ceb3a47df0961bec6196fd0]
stable/4.19: [a02e1404e27855089d2b0a0acc4652c2ce65fe46]
stable/5.10: [9f329d0d6c91142cf0ad08d23c72dd195db2633c]
stable/5.15: [e79ff8c68acb1eddf709d3ac84716868f2a91012]
stable/5.4: [975774ea7528b489930b76a77ffc4d5379b95ff2]

CVE-2021-46923: fs/mount_setattr: always cleanup mount_kattr

Announce: https://lore.kernel.org/linux-cve-announce/2024022745-CVE-2021-46923-a1ec@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Make sure that finish_mount_kattr() is called after mount_kattr was
succesfully built in both the success and failure case to prevent
leaking any references we took when we built it.  We returned early if
path lookup failed thereby risking to leak an additional reference we
took when building mount_kattr when an idmapped mount was requested.

Introduced by commit 9caccd4 ("fs: introduce MOUNT_ATTR_IDMAP") in
5.12-rc1-dontuse.
This commit is not backported to older stable kernels.
Fixed in 5.16-rc8.

Fixed status
mainline: [012e332286e2bb9f6ac77d195f17e74b2963d663]
stable/5.15: [47b5d0a7532d39e42a938f81e3904268145c341d]

CVE-2021-46969: bus: mhi: core: Fix invalid error returning in mhi_queue

Announce: https://lore.kernel.org/linux-cve-announce/2024022720-CVE-2021-46969-3263@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
bus: mhi: core: Fix invalid error returning in mhi_queue mhi_queue
returns an error when the doorbell is not accessible in the current
state. This can happen when the device is in non M0 state, like M3,
and needs to be waken-up prior ringing the DB. This case is managed
earlier by triggering an asynchronous M3 exit via controller
resume/suspend
callbacks, that in turn will cause M0 transition and DB update. So,
since it's not an error but just delaying of doorbell update, there is
no
reason to return an error. This also fixes a use after free error for
skb case, indeed a caller queuing skb will try to free the skb if the
queueing fails, but in that case queueing has been done.

Introduced by commit a8f75cb ("mhi: core: Factorize mhi queuing") in
5.12-rc1-dontuse.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [0ecc1c70dcd32c0f081b173a1a5d89952686f271]

CVE-2021-46972: ovl: fix leaked dentry

Announce: https://lore.kernel.org/linux-cve-announce/2024022721-CVE-2021-46972-2ec2@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Since commit 6815f479ca90 ("ovl: use only uppermetacopy state in
ovl_lookup()"), overlayfs doesn't put temporary dentry when there is a
metacopy error, which leads to dentry leaks when shutting down the
related superblock.

Introduced by commit 6815f47 ("ovl: use only uppermetacopy state in
ovl_lookup()") in 5.8-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [eaab1d45cdb4bb0c846bd23c3d666d5b90af7b41]
stable/5.10: [71d58457a8afc650da5d3292a7f7029317654d95]

CVE-2021-46973: net: qrtr: Avoid potential use after free in MHI send

Announce: https://lore.kernel.org/linux-cve-announce/2024022721-CVE-2021-46973-20ce@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

It is possible that the MHI ul_callback will be invoked immediately
following the queueing of the skb for transmission, leading to the
callback decrementing the refcount of the associated sk and freeing the skb.
As such the dereference of skb and the increment of the sk refcount
must happen before the skb is queued, to avoid the skb to be used
after free
and potentially the sk to drop its last refcount..

Introduced by commit 6e728f3 ("net: qrtr: Add MHI transport layer") in 5.8-rc1.
This commit is not backported to older stable kernels.
Fixed in 5.13-rc1.

Fixed status
mainline: [47a017f33943278570c072bc71681809b2567b3a]
stable/5.10: [48ec949ac979b4b42d740f67b6177797af834f80]

* Updated CVEs

CVE-2019-12379: consolemap: Fix a memory leaking bug in
drivers/tty/vt/consolemap.c

Added mainline fixed commit. It was fixed in 5.3-rc1.

Fixed status
mainline: [84ecc2f6eb1cb12e6d44818f94fa49b50f06e6ac]

CVE-2019-12455: clk-sunxi: fix a missing-check bug in sunxi_divs_clk_setup()

Added mainline fixed commit. It was fixed in 5.3-rc1.

Fixed status
mainline: [fcdf445ff42f036d22178b49cf64e92d527c1330]

CVE-2021-3542: media: firewire: firedtv-avc: fix a buffer overflow in
avc_ca_pmt()

Add mainline, 4.19, 5.10, 5.15, and 5.4 fixed commit.

Fixed status
mainline: [35d2969ea3c7d32aee78066b1f3cf61a0d935a4e]
stable/4.19: [53ec9dab4eb0a8140fc85760fb50effb526fe219]
stable/5.10: [d7fc85f6104259541ec136199d3bf7c8a736613d]
stable/5.15: [cb667140875a3b1db92e4c50b4617a7cbf84659b]
stable/5.4: [2461f38384d50dd966e1db44fe165b1896f5df5a]

CVE-2022-3642: wifi: rtl8xxxu: Fix reads of uninitialized variables
hw_ctrl_s1, sw_ctrl_s1

Added mainline fixed commit. It was fixed in 6.2-rc1.

Fixed status
mainline: [80e5acb6dd72b25a6e6527443b9e9c1c3a7bcef6]

CVE-2021-33630: net/sched: cbs: Fix not adding cbs instance to list

4.19 was fixed.

Fixed status
mainline: [3e8b9bfa110896f95d602d8c98d5f9d67e41d78c]
stable/4.19: [bbd8e460c478adbc88e2ec4e2414931a59791348]

CVE-2023-52429: dm: limit the number of targets and parameter size area

stable 5.10, 5.15, 6.1, 6.6, and 6.7 were fixed.

Fixed status
mainline: [bd504bcfec41a503b32054da5472904b404341a4]
stable/5.10: [a891a0621e725e85529985139cada8cb5a74a116]
stable/5.15: [888a0a46b80fa37eacfe81faf47ba0b83876251d]
stable/6.1: [c5d83ac2bf6ca668a39ffb1a576899a66153ba19]
stable/6.6: [438d19492b7f002334573bae43276297eb234c80]
stable/6.7: [cd70175481f63af31901dd463e44386f033c3f4c]

CVE-2023-52434: smb: client: fix potential OOBs in smb2_parse_contexts()

stable 6.1 was fixed.

Fixed status
mainline: [af1689a9b7701d9907dfc84d2a4b57c4bc907144]
stable/6.1: [1ae3c59355dc9882e09c020afe8ffbd895ad0f29]
stable/6.6: [17a0f64cc02d4972e21c733d9f21d1c512963afa]

CVE-2023-52435: net: prevent mss overflow in skb_segment()

stable 5.10, 5.15, 5.4, and 6.1 were fixed.

Fixed status
mainline: [23d05d563b7e7b0314e65c8e882bc27eac2da8e7]
stable/5.10: [8f8f185643747fbb448de6aab0efa51c679909a3]
stable/5.15: [6c53e8547687d9c767c139cd4b50af566f58c29a]
stable/5.4: [cd1022eaf87be8e6151435bd4df4c242c347e083]
stable/6.1: [989b0ff35fe5fc9652ee5bafbe8483db6f27b137]
stable/6.6: [95b3904a261a9f810205da560e802cc326f50d77]

CVE-2023-52437: Revert "md/raid5: Wait for MD_SB_CHANGE_PENDING in raid5d"

stable 4.19, 5.10, and 5.4 were fixed.

Fixed status
mainline: [bed9e27baf52a09b7ba2a3714f1e24e17ced386d]
stable/4.19: [1e8c1c2a92692881ac7ec92dcf1c8a846584251b]
stable/5.10: [88ec9bbcd33c21d30becd9d2949e8158f47660cd]
stable/5.15: [0ee3ded745ca8ce68e107d9b5e5d33938e091003]
stable/5.4: [7f71d9817cea3582daa2e903596461f5f5d0c022]
stable/6.1: [bed0acf330b2c50c688f6d9cfbcac2aa57a8e613]
stable/6.6: [e16a0bbdb7e590a6607b0d82915add738c03c069]
stable/6.7: [0de40f76d567133b871cd6ad46bb87afbce46983]

CVE-2024-0340: vhost: use kzalloc() instead of kmalloc() followed by memset()

stable 4.19, 5.10, 5.15, and 5.4.

Fixed status
mainline: [4d8df0f5f79f747d75a7d356d9b9ea40a4e4c8a9]
stable/4.19: [95eab1039625d54d1770665756dd34e9fe926638]
stable/5.10: [cda4ca038cafe016bd8dcac8cac83d771dfdcbf0]
stable/5.15: [be38f291fd4d106be66370debd23d625c576023e]
stable/5.4: [88c7e1e7a6b82d38ff82ca446862f3d5de34192a]
stable/6.1: [4675661672e3730597babf97c4e9593a775c8917]

CVE-2024-0607: netfilter: nf_tables: fix pointer math issue in
nft_byteorder_eval()

stable 4.19, 5.10, and 5.4.

Fixed status
mainline: [c301f0981fdd3fd1ffac6836b423c4d7a8e0eb63]
stable/4.19: [fca41e5b687e029f69e3a35a2fa31e2560e538dc]
stable/5.10: [9a865a11d6890d4a789db1eaafebdc8bd092b12c]
stable/5.15: [b8b514b2a6cdfac24911e4910461bcb9db15ca8d]
stable/5.4: [25b42be4e067e107a2559266b54bf07fa5b094fb]
stable/6.1: [18a169810cff769a7a697b35058c756805f589e0]
stable/6.6: [013deed31ab15ef287b0045e4e7bd8f250e75b94]

CVE-2024-1086: netfilter: nf_tables: reject QUEUE/DROP verdict parameters

stable 4.19, 5.10, 5.15, and 5.4.

Fixed status
mainline: [f342de4e2f33e0e39165d8639387aa6c19dff660]
stable/4.19: [8365e9d92b85fda975a5ece7a3a139cb964018c8]
stable/5.10: [55a60251fa50d4e68175e36666b536a602ce4f6c]
stable/5.15: [960cf4f812530f01f6acc6878ceaa5404c06af7b]
stable/5.4: [4e66422f1b56149761dc76030e6345d1cca6f869]
stable/6.1: [8e34430e33b8a80bc014f3efe29cac76bc30a4b4]
stable/6.6: [6653118b176a00915125521c6572ae8e507621db]
stable/6.7: [f05a497e7bc8851eeeb3a58da180ba469efebb05]

CVE-2024-1151: net: openvswitch: limit the number of recursions from action sets

stable 5.10, 5.15 6.1, 6.6, and 6.7 were fixed.

Fixed status
mainline: [6e2f90d31fe09f2b852de25125ca875aabd81367]
stable/5.10: [55cfccb658fc142d7fbfeae2d0496b7841d128c3]
stable/5.15: [c45f2fa92cb273f77be33b60a120ff7cf6df8085]
stable/6.1: [65ded4eb220695909eee657758e824fc30f0b561]

CVE-2024-23849: net/rds: Fix UBSAN: array-index-out-of-bounds in rds_cmsg_recv

stable 4.19, 5.10, 5.15, and 5.4.

Fixed status
mainline: [13e788deb7348cc88df34bed736c3b3b9927ea52]
stable/4.19: [344350bfa3b4b37d7c3d5a00536e6fbf0e953fbf]
stable/5.10: [5ae8d50044633306ff160fcf7faa24994175efe1]
stable/5.15: [00d1ee8e1d02194f7b7b433e904e04bbcd2cc0dc]
stable/5.4: [a37ae111db5e0f7e3d6b692056c30e3e0f6f79cd]
stable/6.1: [71024928b3f71ce4529426f8692943205c58d30b]
stable/6.6: [7a73190ea557e7f26914b0fe04c1f57a96cb771f]
stable/6.7: [0b787c2dea15e7a2828fa3a74a5447df4ed57711]

CVE-2024-23850: btrfs: do not ASSERT() if the newly created subvolume
already got read

stable 5.10, 5.15, 6.1, 6.6, and 6.7 were fixed.

Fixed status
mainline: [e03ee2fe873eb68c1f9ba5112fee70303ebf9dfb]
stable/5.10: [3f5d47eb163bceb1b9e613c9003bae5fefc0046f]
stable/5.15: [e31546b0f34af21738c4ceac47d662c00ee6382f]
stable/6.1: [66b317a2fc45b2ef66527ee3f8fa08fb5beab88d]
stable/6.6: [833775656d447c545133a744a0ed1e189ce61430]
stable/6.7: [5a172344bfdabb46458e03708735d7b1a918c468]

CVE-2024-23851: Kernel crash in drivers/md/dm-ioctl.c when allocate
memory more than INT_MAX bytes

stable 5.10, 5.15, and 6.1 were fixed.

Fixed status
mainline: [bd504bcfec41a503b32054da5472904b404341a4]
stable/5.10: [a891a0621e725e85529985139cada8cb5a74a116]
stable/5.15: [888a0a46b80fa37eacfe81faf47ba0b83876251d]
stable/6.1: [c5d83ac2bf6ca668a39ffb1a576899a66153ba19]
stable/6.6: [438d19492b7f002334573bae43276297eb234c80]
stable/6.7: [cd70175481f63af31901dd463e44386f033c3f4c]

CVE-2024-26581: netfilter: nft_set_rbtree: skip end interval element from gc

stable 5.10, 5.15, 5.4, 6.1, 6.6, and 6.7 were fixed.

Fixed status
mainline: [60c0c230c6f046da536d3df8b39a20b9a9fd6af0]
stable/5.10: [4cee42fcf54fec46b344681e7cc4f234bb22f85a]
stable/5.15: [2bab493a5624444ec6e648ad0d55a362bcb4c003]
stable/5.4: [10e9cb39313627f2eae4cd70c4b742074e998fd8]
stable/6.1: [1296c110c5a0b45a8fcf58e7d18bc5da61a565cb]
stable/6.6: [b734f7a47aeb32a5ba298e4ccc16bb0c52b6dbf7]
stable/6.7: [6eb14441f10602fa1cf691da9d685718b68b78a9]

CVE-2024-26582: net: tls: fix use-after-free with partial reads and
async decrypt

stable 6.1, 6.6, and 6.7 were fixed.

Fixed status
mainline: [32b55c5ff9103b8508c1e04bfa5a08c64e7a925f]
stable/6.1: [20b4ed034872b4d024b26e2bc1092c3f80e5db96]
stable/6.6: [d684763534b969cca1022e2a28645c7cc91f7fa5]
stable/6.7: [754c9bab77a1b895b97bd99d754403c505bc79df]

CVE-2024-26583: tls: fix race between async notify and socket close

stable 6.1, 6.6, and 6.7 were fixed.

Fixed status
mainline: [aec7961916f3f9e88766e2688992da6980f11b8d]
stable/6.1: [7a3ca06d04d589deec81f56229a9a9d62352ce01]
stable/6.6: [86dc27ee36f558fe223dbdfbfcb6856247356f4a]
stable/6.7: [6209319b2efdd8524691187ee99c40637558fa33]

CVE-2024-26584: net: tls: handle backlogging of crypto requests

stable 6.6 and 6.7 were fixed.

Fixed status
mainline: [8590541473188741055d27b955db0777569438e3]
stable/6.6: [13eca403876bbea3716e82cdfe6f1e6febb38754]
stable/6.7: [ab6397f072e5097f267abf5cb08a8004e6b17694]

CVE-2024-26585: tls: fix race between tx work scheduling and socket close

stable 6.6 and 6.7 were fixed.

Fixed status
mainline: [e01e3934a1b2d122919f73bc6ddbe1cdafc4bbdb]
stable/6.6: [6db22d6c7a6dc914b12c0469b94eb639b6a8a146]
stable/6.7: [e327ed60bff4a991cd7a709c47c4f0c5b4a4fd57]

Currently tracking CVEs

CVE-2021-31615: Unencrypted Bluetooth Low Energy baseband links in
Bluetooth Core Specifications 4.0 through 5.2

There is no fix information.

CVE-2020-26556: kernel: malleable commitment Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26557: kernel: predictable Authvalue in Bluetooth Mesh
Provisioning Leads to MITM

No fix information.

CVE-2020-26559: kernel: Authvalue leak in Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26560: kernel: impersonation attack in Bluetooth Mesh Provisioning

No fix information.

Regards,
-- 
Masami Ichikawa
Cybertrust Japan Co., Ltd.

Email :masami.ichikawa@cybertrust.co.jp
          :masami.ichikawa@miraclelinux.com


^ permalink raw reply	[flat|nested] 33+ messages in thread

* [kernel-cve-report] New CVE entries this week
@ 2024-02-22  0:31 Masami Ichikawa
  0 siblings, 0 replies; 33+ messages in thread
From: Masami Ichikawa @ 2024-02-22  0:31 UTC (permalink / raw)
  To: cip-dev

Hi!

It's this week's CVE report.

This week reported 15 new CVEs and 2 updated CVEs.

* New CVEs

CVE-2023-52433: netfilter: nft_set_rbtree: skip sync GC for new
elements in this transaction

Announce: https://lore.kernel.org/linux-cve-announce/2024022058-outsell-equator-e1c5@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
netfilter: nft_set_rbtree: skip sync GC for new elements in this
transaction New elements in this transaction might expired before such
transaction ends.
Skip sync GC for such elements otherwise commit path might walk over
an already released object. Once transaction is finished,
async GC will collect such expired element.

This bug was introduced by commit f6c383b ("netfilter: nf_tables:
adapt set backend to use GC transaction API") in 6.5-rc6.
This patch is not backported to 4.x kernels. Therefore, 4.19, 4.14,
and 4.4 are not affected.

Fixed by commit 2ee52ae ("netfilter: nft_set_rbtree: skip sync GC for
new elements in this transaction") in 6.6-rc1.

Fixed status
mainline: [2ee52ae94baabf7ee09cf2a8d854b990dac5d0e4]
stable/5.10: [c323ed65f66e5387ee0a73452118d49f1dae81b8]
stable/5.15: [9af7dfb3c9d7985172a240f85e684c5cd33e29ce]
stable/5.4: [03caf75da1059f0460666c826e9f50e13dfd0017]
stable/6.1: [9a8c544158f68f656d1734eb5ba00c4f817b76b1]

CVE-2023-52434: smb: client: fix potential OOBs in smb2_parse_contexts()

Announce: https://lore.kernel.org/linux-cve-announce/2024022033-makeshift-flammable-cb72@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

An OOB bug was found in smb2_parse_contexts(). The
smb2_parse_contexts() needed to validate offsets and lengths before
creating contexts.

Fixed by commit af1689a ("smb: client: fix potential OOBs in
smb2_parse_contexts()") in 6.7-rc6.

Fixed status
mainline: [af1689a9b7701d9907dfc84d2a4b57c4bc907144]
stable/6.6: [17a0f64cc02d4972e21c733d9f21d1c512963afa]

CVE-2023-52435: net: prevent mss overflow in skb_segment()

Announce: https://lore.kernel.org/linux-cve-announce/2024022048-rind-huff-b1a2@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Invalid mss value causes invalid page access when calculating
partial_segs in slb segment().
Added length check to prevent length size should be smaller than GSO_BY_FRAGS.

This bug was introduced by commit 3953c46 ("sk_buff: allow segmenting
based on frag sizes") in 4.8-rc1.
This commit is not backported to 4.4 so 4.4 kernels are not affected.

Fixed by commit 23d05d5 ("net: prevent mss overflow in skb_segment()
") in 6.7-rc6.

Fixed status
mainline: [23d05d563b7e7b0314e65c8e882bc27eac2da8e7]
stable/6.6: [95b3904a261a9f810205da560e802cc326f50d77]

CVE-2023-52436: f2fs: explicitly null-terminate the xattr list

Announce: https://lore.kernel.org/linux-cve-announce/2024022056-operative-cork-082c@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
f2fs: explicitly null-terminate the xattr list When setting an xattr,
explicitly null-terminate the xattr list. This eliminates the fragile
assumption that the unused xattr space is always zeroed.

Fixed by commit e26b6d3 ("f2fs: explicitly null-terminate the xattr
list") in 6.8-rc1.

It seems as if 4.4 kernels are affected too.

Fixed status
mainline: [e26b6d39270f5eab0087453d9b544189a38c8564]
stable/4.19: [16ae3132ff7746894894927c1892493693b89135]
stable/5.10: [3e47740091b05ac8d7836a33afd8646b6863ca52]
stable/5.15: [32a6cfc67675ee96fe107aeed5af9776fec63f11]
stable/5.4: [12cf91e23b126718a96b914f949f2cdfeadc7b2a]
stable/6.1: [5de9e9dd1828db9b8b962f7ca42548bd596deb8a]
stable/6.6: [2525d1ba225b5c167162fa344013c408e8b4de36]
stable/6.7: [f6c30bfe5a49bc38cae985083a11016800708fea]

CVE-2023-52437: Revert "md/raid5: Wait for MD_SB_CHANGE_PENDING in raid5d"

Announce: https://lore.kernel.org/linux-cve-announce/2024022009-subsoil-halt-4b28@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

The commit 5e2cf33 ("md/raid5: Wait for MD_SB_CHANGE_PENDING in
raid5d") causes a deadlock bug. So revert 5e2cf33 to fix the deadlock.
The commit 5e2cf33 is not backported to 4.4 so 4.4 kernels are not affected.

Fixed by commit bed9e27 ("Revert "md/raid5: Wait for
MD_SB_CHANGE_PENDING in raid5d"") in 6.8-rc1.

Fixed status
mainline: [bed9e27baf52a09b7ba2a3714f1e24e17ced386d]
stable/5.15: [0ee3ded745ca8ce68e107d9b5e5d33938e091003]
stable/6.1: [bed0acf330b2c50c688f6d9cfbcac2aa57a8e613]
stable/6.6: [e16a0bbdb7e590a6607b0d82915add738c03c069]
stable/6.7: [0de40f76d567133b871cd6ad46bb87afbce46983]

CVE-2023-52438: binder: fix use-after-free in shinker's callback

Announce: https://lore.kernel.org/linux-cve-announce/2024022017-slit-wish-e5d7@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

A use-after-free bug was found in the binder driver.
This bug was introduced by commit dd2283f ("mm: mmap: zap pages with
read mmap_sem in munmap") in 4.20-rc1.
The commit dd2283f is not backported to 4.x kernels so that kernel 4.x
are not affected.

Fixed by commit 3f489c2 ("binder: fix use-after-free in shinker's
callback") in 6.8-rc1.

Fixed status
mainline: [3f489c2067c5824528212b0fc18b28d51332d906]
stable/5.10: [c8c1158ffb007197f31f9d9170cf13e4f34cbb5c]
stable/5.15: [8ad4d580e8aff8de2a4d57c5930fcc29f1ffd4a6]
stable/5.4: [a53e15e592b4dcc91c3a3b8514e484a0bdbc53a3]
stable/6.1: [9fa04c93f24138747807fe75b5591bb680098f56]
stable/6.6: [a49087ab93508b60d9b8add91707a22dda832869]
stable/6.7: [e074686e993ff1be5f21b085a3b1b4275ccd5727]

CVE-2023-52439: uio: Fix use-after-free in uio_open

Announce: https://lore.kernel.org/linux-cve-announce/2024022026-wobbling-jumbo-748e@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

A race condition bug causes use-after-free vulnerability in the uio_open().

This bug was introduced by commit 57c5f4d ("uio: fix crash after the
device is unregistered") in 4.18-rc5.
The commit 57c5f4d is not backported to 4.4 kernels so that 4.4
kernels are not affected.

Fixed by commit 0c9ae0b ("uio: Fix use-after-free in uio_open") in 6.8-rc1.

Fixed status
mainline: [0c9ae0b8605078eafc3bea053cc78791e97ba2e2]
stable/4.19: [3174e0f7de1ba392dc191625da83df02d695b60c]
stable/5.10: [5e0be1229ae199ebb90b33102f74a0f22d152570]
stable/5.15: [5cf604ee538ed0c467abe3b4cda5308a6398f0f7]
stable/5.4: [e93da893d52d82d57fc0db2ca566024e0f26ff50]
stable/6.1: [17a8519cb359c3b483fb5c7367efa9a8a508bdea]
stable/6.6: [35f102607054faafe78d2a6994b18d5d9d6e92ad]
stable/6.7: [913205930da6213305616ac539447702eaa85e41]

CVE-2024-26581: netfilter: nft_set_rbtree: skip end interval element from gc

Announce: https://lore.kernel.org/linux-cve-announce/2024022024-uniquely-recluse-d893@gregkh/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
netfilter: nft_set_rbtree: skip end interval element from
gc rbtree lazy gc on insert might collect an end interval element that
has been just added in this transactions,
skip end interval elements that are not yet active.

The commit f718863 is not backported to 4.x kernels so that 4.x
kernels are not affected.
Fixed by commit 60c0c23 ("netfilter: nft_set_rbtree: skip end interval
element from gc") in 6.8-rc4.

Fixed status
mainline: [60c0c230c6f046da536d3df8b39a20b9a9fd6af0]
stable/6.1: [1296c110c5a0b45a8fcf58e7d18bc5da61a565cb]
stable/6.6: [b734f7a47aeb32a5ba298e4ccc16bb0c52b6dbf7]
stable/6.7: [6eb14441f10602fa1cf691da9d685718b68b78a9]

CVE-2023-52440: ksmbd: fix slub overflow in ksmbd_decode_ntlmssp_auth_blob()

Announce: https://lore.kernel.org/linux-cve-announce/2024022123-glance-wrinkle-26c1@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
ksmbd: fix slub overflow in ksmbd_decode_ntlmssp_auth_blob()
If authblob->SessionKey.Length is bigger than session key
size(CIFS_KEY_SIZE), slub overflow can happen in key exchange codes.
cifs_arc4_crypt copy to session key array from SessionKey from client.

Fixed by commit 4b081ce0 ("ksmbd: fix slub overflow in
ksmbd_decode_ntlmssp_auth_blob()") in 6.6-rc1.
The ksmbd was introduced in 5.15 so prior to this version is not affected.

Fixed status
mainline: [4b081ce0d830b684fdf967abc3696d1261387254]
stable/5.15: [bd554ed4fdc3d38404a1c43d428432577573e809]
stable/6.1: [30fd6521b2fbd9b767e438e31945e5ea3e3a2fba]

CVE-2023-52441: ksmbd: fix out of bounds in init_smb2_rsp_hdr()

Announce: https://lore.kernel.org/linux-cve-announce/2024022129-gently-activity-ca7d@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
ksmbd: fix out of bounds in init_smb2_rsp_hdr()
If client send smb2 negotiate request and then send smb1 negotiate
request, init_smb2_rsp_hdr is called for smb1
negotiate request since need_neg is set to false. This patch ignore
smb1 packets after ->need_neg is set to false.

Fixed by commit 536bb492 ("ksmbd: fix out of bounds in
init_smb2_rsp_hdr()") in 6.5-rc4.
The ksmbd was introduced in 5.15 so prior to this version is not affected.

Fixed status
mainline: [536bb492d39bb6c080c92f31e8a55fe9934f452b]
stable/5.15: [5c0df9d30c289d6b9d7d44e2a450de2f8e3cf40b]
stable/6.1: [330d900620dfc9893011d725b3620cd2ee0bc2bc]

CVE-2023-52442: ksmbd: validate session id and tree id in compound request

Announce: https://lore.kernel.org/linux-cve-announce/2024022132-unvented-arguably-5ea9@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
ksmbd: validate session id and tree id in
compound request `smb2_get_msg()` in smb2_get_ksmbd_tcon() and
smb2_check_user_session() will always return
the first request smb2 header in a compound request. if
`SMB2_TREE_CONNECT_HE` is the first command in compound
request, will return 0, i.e. The tree id check is skipped. This patch
use ksmbd_req_buf_next() to get current
command in compound.

Fixed by commit 3df0411 ("ksmbd: validate session id and tree id in
compound request") in 6.5-rc4.
The ksmbd was introduced in 5.15 so prior to this version is not affected.

Fixed status
mainline: [3df0411e132ee74a87aa13142dfd2b190275332e]
stable/5.15: [017d85c94f02090a87f4a473dbe0d6ee0da72693]
stable/6.1: [becb5191d1d5fdfca0198a2e37457bbbf4fe266f]

CVE-2024-26582: net: tls: fix use-after-free with partial reads and
async decrypt

Announce: https://lore.kernel.org/linux-cve-announce/2024022139-spruce-prelude-c358@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
net: tls: fix use-after-free with partial reads
and async decrypt tls_decrypt_sg doesn't take a reference on the pages
from clear_skb, so the put_page() in
tls_decrypt_done releases them, and we trigger a use-after-free in
process_rx_list when we try to read from the
partially-read skb.

This bug was introduced by commit fd31f39 ("tls: rx: decrypt into a
fresh skb") in 6.0-rc1.
This commit is not backported to 5.x and 4.x kernels.

Fixed by commit 32b55c ("net: tls: fix use-after-free with partial
reads and async decrypt") in 6.8-rc5.

Fixed status
mainline: [32b55c5ff9103b8508c1e04bfa5a08c64e7a925f]

CVE-2024-26583: tls: fix race between async notify and socket close

Announce: https://lore.kernel.org/linux-cve-announce/2024022146-traction-unjustly-f451@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
tls: fix race between async notify and socket
close The submitting thread (one which called recvmsg/sendmsg) may
exit as soon as the async crypto handler calls
complete() so any code past that point risks touching already freed
data. Try to avoid the locking and extra flags
altogether. Have the main thread hold an extra reference, this way we
can depend solely on the atomic ref counter
for synchronization. Don't futz with reiniting the completion, either,
we are now tightly controlling when
completion fires.

This bug was introduced by commit 0cada33 ("net/tls: fix race
condition causing kernel panic") in 5.7.
This commit was backported to 5.4 but not to 4.x kernels. so kernel
4.x are not affected.

Fixed by commit aec7961 ("tls: fix race between async notify and
socket close") in 6.8-rc5.

Fixed status
mainline: [aec7961916f3f9e88766e2688992da6980f11b8d]

CVE-2024-26584: net: tls: handle backlogging of crypto requests

Announce: https://lore.kernel.org/linux-cve-announce/2024022148-showpiece-yanking-107c@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
net: tls: handle backlogging of crypto requests
Since we're setting the CRYPTO_TFM_REQ_MAY_BACKLOG flag on our
requests to the crypto API, crypto_aead_{encrypt,decrypt}
can return -EBUSY instead of -EINPROGRESS in valid situations. For
example, when the cryptd queue for AESNI is full
(easy to trigger with an artificially low cryptd.cryptd_max_cpu_qlen),
requests will be enqueued to the backlog but still
processed. In that case, the async callback will also be called twice:
first with err == -EINPROGRESS, which it seems we
can just ignore, then with err == 0. Compared to Sabrina's original
patch this version uses the new tls_*crypt_async_wait()
helpers and converts the EBUSY to EINPROGRESS to avoid having to
modify all the error handling paths. The handling is identical.

This bug was introduced by a54667f ("tls: Add support for encryption
using async offload accelerator") in 4.16-rc1
This patch is not backported to 4.4.

Fixed by commit 8590541 ("net: tls: handle backlogging of crypto
requests") oin 6.8-rc5.

Fixed status
mainline: [8590541473188741055d27b955db0777569438e3]

CVE-2024-26585: tls: fix race between tx work scheduling and socket close

Announce: https://lore.kernel.org/linux-cve-announce/2024022150-fancy-numerate-94ab@gregkh/T/#u
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel, the following vulnerability has been resolved:
tls: fix race between tx work scheduling and
socket close Similarly to previous commit, the submitting thread
(recvmsg/sendmsg) may exit as soon as the async
crypto handler calls complete(). Reorder scheduling the work before
calling complete(). This seems more logical
in the first place, as it's the inverse order of what the submitting
thread will do.

This bug was introduced by commit a42055e ("net/tls: Add support for
async encryption of records for performance")
in 4.20-rc1. Linux 4.19, and 4.4 are not affected.

Fixed by commit e01e393 ("tls: fix race between tx work scheduling and
socket close") in 6.8-rc5.

Fixed status
mainline: [e01e3934a1b2d122919f73bc6ddbe1cdafc4bbdb]

* Updated CVEs

CVE-2024-0340: vhost: use kzalloc() instead of kmalloc() followed by memset()

stable/6.1 was fixed.

Fixed status
mainline: [4d8df0f5f79f747d75a7d356d9b9ea40a4e4c8a9]
stable/6.1: [4675661672e3730597babf97c4e9593a775c8917]

CVE-2024-1151: net: openvswitch: limit the number of recursions from action sets

Fixed in 6.8-rc5.

Fixed status
mainline: [6e2f90d31fe09f2b852de25125ca875aabd81367]

Currently tracking CVEs

CVE-2021-31615: Unencrypted Bluetooth Low Energy baseband links in
Bluetooth Core Specifications 4.0 through 5.2

There is no fix information.

CVE-2020-26556: kernel: malleable commitment Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26557: kernel: predictable Authvalue in Bluetooth Mesh
Provisioning Leads to MITM

No fix information.

CVE-2020-26559: kernel: Authvalue leak in Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26560: kernel: impersonation attack in Bluetooth Mesh Provisioning

No fix information.

Regards,
-- 
Masami Ichikawa
Cybertrust Japan Co., Ltd.

Email :masami.ichikawa@cybertrust.co.jp
          :masami.ichikawa@miraclelinux.com


^ permalink raw reply	[flat|nested] 33+ messages in thread

* [kernel-cve-report] New CVE entries this week
@ 2024-02-14 22:47 Masami Ichikawa
  0 siblings, 0 replies; 33+ messages in thread
From: Masami Ichikawa @ 2024-02-14 22:47 UTC (permalink / raw)
  To: cip-dev

Hi!

It's this week's CVE report.

This week reported 7 new CVEs and 2 updated CVEs.

FYI:
The Linux kernel project has been accepted as a CNA
(http://www.kroah.com/log/blog/2024/02/13/linux-is-a-cna/).
CVEs will be announced to the linux-cve-announce mailing
list(https://lore.kernel.org/linux-cve-announce/).

* New CVEs

CVE-2024-1312: mm: lock_vma_under_rcu() must check vma->anon_vma under vma lock

CVSS v3(NIST): N/A
CVSS v3(CNA): 5.1(MEDIUM)

A use-after-free flaw was found in the Linux kernel's Memory
Management subsystem when a user wins two races at the same time with
a fail in the mas_prev_slot function.
This issue could allow a local user to crash the system.

This bug was introduced by commit 5e31275 ("mm: add per-VMA lock and
helper functions to control it") in 6.4-rc1.
It was fixed in 6.5-rc4. So, it affects 6.4-rc1 to 6.5-rc3.

Fixed status
mainline: [657b5146955eba331e01b9a6ae89ce2e716ba306]

CVE-2024-1151: net: openvswitch: limit the number of recursions from action sets

CVSS v3(NIST): N/A
CVSS v3(CNA): 5.5(MEDIUM)

A vulnerability was reported in the Open vSwitch sub-component in the
Linux Kernel. The flaw occurs when a recursive operation of code push
recursively calls into the code block.
The OVS module does not validate the stack depth, pushing too many
frames and causing a stack overflow. As a result, this can lead to a
crash or other related issues.

This bug was introduced by commit 798c166173ff ("openvswitch: Optimize
sample action for the clone use cases") in 4.12-rc1.
Linux 4.4 isn't affected.

Fixed status
Patch is available on the netdev mailing
list(https://lore.kernel.org/all/20240207132416.1488485-1-aconole@redhat.com/)
but it hasn't been merged into the mainline yet.

CVE-2023-52429: dm: limit the number of targets and parameter size area

CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

dm_table_create in drivers/md/dm-table.c in the Linux kernel through
6.7.4 can attempt to (in alloc_targets) allocate more than INT_MAX
bytes, and crash,
because of a missing check for struct dm_ioctl.target_count.

It was fixed in 6.8-rc3.

Fixed status
mainline: [bd504bcfec41a503b32054da5472904b404341a4]

CVE-2024-25739: ubi: Check for too small LEB size in VTBL code

CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

create_empty_lvol in drivers/mtd/ubi/vtbl.c in the Linux kernel
through 6.7.4 can attempt to allocate zero bytes, and crash, because
of a missing check for ubi->leb_size.

Fixed status
Patch is available on the lkml
(https://www.spinics.net/lists/kernel/msg5074816.html) but it hasn't
been merged yet.

CVE-2024-25740: memory leak in ubi_attach

CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

A memory leak flaw was found in the UBI driver in
drivers/mtd/ubi/attach.c in the Linux kernel through 6.7.4 for
UBI_IOCATT, because kobj->name is not released.

Fixed status
Not fixed yet

CVE-2024-25741: usb/f_printer: WARNING in usb_ep_queue

CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

printer_write in drivers/usb/gadget/function/f_printer.c in the Linux
kernel through 6.7.4 does not properly call usb_ep_queue, which might
allow attackers to cause
a denial of service or have unspecified other impact.

Fixed status
Not fixed yet.

CVE-2024-25744: x86/coco: Disable 32-bit emulation by default on TDX and SEV

CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel before 6.6.7, an untrusted VMM can trigger int80
syscall handling at any given point. This is related to
arch/x86/coco/tdx/tdx.c and
arch/x86/mm/mem_encrypt_amd.c.

This bug was introduced by commit 1da5c9b ("x86: Introduce
ia32_enabled()") in 6.7-rc1. This commit was backported to 6.1 and 6.6
but not backported to 5.x and 4.x kernels.
This bug was fixed in 6.7-rc5.

Fixed status
mainline: [b82a8dbd3d2f4563156f7150c6f2ecab6e960b30]
stable/6.1: [b8ec27ae221eee458b15b700706db311474ac619]
stable/6.6: [34c686e5be2fa1c03ae09568159a9ef37d1c7cf5]


* Updated CVEs

CVE-2024-23850: btrfs: do not ASSERT() if the newly created subvolume
already got read

Fixed in the mainline. This bug was introduced by commit 2dfb1e4
("btrfs: preallocate anon block device at first phase of snapshot
creation") in 5.9-rc1.
The commit 2dfb1e4 is not backported to before 5.9 so these kernels
are not affected.

Fixed status
mainline: [e03ee2fe873eb68c1f9ba5112fee70303ebf9dfb]

CVE-2024-24855: NULL pointer dereference bug was found in scsi device driver

Added fixed commit to the mainline. This commit was merged in 6.5-rc2.

Fixed status
mainline: [0e881c0a4b6146b7e856735226208f48251facd8]

Currently tracking CVEs

CVE-2021-31615: Unencrypted Bluetooth Low Energy baseband links in
Bluetooth Core Specifications 4.0 through 5.2

There is no fix information.

CVE-2020-26556: kernel: malleable commitment Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26557: kernel: predictable Authvalue in Bluetooth Mesh
Provisioning Leads to MITM

No fix information.

CVE-2020-26559: kernel: Authvalue leak in Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26560: kernel: impersonation attack in Bluetooth Mesh Provisioning

No fix information.

Regards,
-- 
Masami Ichikawa
Cybertrust Japan Co., Ltd.

Email :masami.ichikawa@cybertrust.co.jp
          :masami.ichikawa@miraclelinux.com


^ permalink raw reply	[flat|nested] 33+ messages in thread

* [kernel-cve-report] New CVE entries this week
@ 2024-02-07 23:05 Masami Ichikawa
  0 siblings, 0 replies; 33+ messages in thread
From: Masami Ichikawa @ 2024-02-07 23:05 UTC (permalink / raw)
  To: cip-dev

Hi!

It's this week's CVE report.

This week reported 10 new CVEs and 3 updated CVEs.

* New CVEs

CVE-2023-6240: Marvin vulnerability side-channel leakage in the RSA
decryption operation

CVSS v3(NIST): N/A
CVSS v3(CNA): 6.5 (MEDIUM)

A Marvin vulnerability side-channel leakage was found in the RSA
decryption operation in the Linux Kernel. This issue may allow a
network attacker to decrypt ciphertexts or forge signatures, limiting
the services that use that private key.

This vulnerability is not only affecting Linux kernel, it is also
affecting lots of softwares.
https://people.redhat.com/~hkario/marvin/

Fixed status
Not fixed yet.

CVE-2024-22386: NULL pointer dereference bug was found in drm/exynos
device driver

CVSS v3(NIST): N/A
CVSS v3(CNA): 5.3 (MEDIUM)

A race condition was found in the Linux kernel's drm/exynos device
driver in exynos_drm_crtc_atomic_disable() function. This can result
in a null pointer dereference issue, possibly leading to a kernel
panic or denial of service issue.

It looks like commit 2e63972a ("drm/exynos: fix a possible
null-pointer dereference due to data race in
exynos_drm_crtc_atomic_disable()") fixes this vulnerability but
accessing to the bugzilla
(https://bugzilla.openanolis.cn/show_bug.cgi?id=8147) is restricted
now so we need to wait for sometime.

Fixed status
Not fixed yet.

CVE-2024-23196: NULL pointer dereference bug was found in sound/hda
device driver

CVSS v3(NIST): N/A
CVSS v3(CNA): 5.3 (MEDIUM)

A race condition was found in the Linux kernel's sound/hda device
driver in snd_hdac_regmap_sync() function. This can result in a null
pointer dereference issue, possibly leading to a kernel panic or
denial of service issue.

It looks like commit 1f4a08fed ("ALSA: hda: fix a possible
null-pointer dereference due to data race in snd_hdac_regmap_sync()")
fixes this vulnerability but accessing to the bugzilla
(https://bugzilla.openanolis.cn/show_bug.cgi?id=8148) is restricted
now so we need to wait for sometime.

Fixed status
Not fixed yet.

CVE-2024-24855: NULL pointer dereference bug was found in scsi device driver

CVSS v3(NIST): N/A
CVSS v3(CNA): 5.0 (MEDIUM)

A race condition was found in the Linux kernel's scsi device driver in
lpfc_unregister_fcf_rescan() function. This can result in a null
pointer dereference issue, possibly leading to a kernel panic or
denial of service issue.

It looks like commit 0e881c0a ("scsi: lpfc: Fix a possible data race
in lpfc_unregister_fcf_rescan()") fixes this vulnerability but
accessing to the bugzilla
(https://bugzilla.openanolis.cn/show_bug.cgi?id=8149) is restricted
now so we need to wait for sometime.

Fixed status
Not fixed yet.

CVE-2024-24857: Integer overflow bug was found in bluetooth device driver

CVSS v3(NIST): N/A
CVSS v3(CNA): 4.6 (MEDIUM)

A race condition was found in the Linux kernel's net/bluetooth device
driver in conn_info_{min,max}_age_set() function. This can result in
integrity overflow issue, possibly leading to bluetooth connection
abnormality or denial of service.

Fixed status
Not fixed yet.

CVE-2024-24858: Race condition bug in
{conn,adv}_{min,max}_interval_set() in bluetooth driver causes DoS

CVSS v3(NIST): N/A
CVSS v3(CNA): 4.6 (MEDIUM)

A race condition was found in the Linux kernel's net/bluetooth in
{conn,adv}_{min,max}_interval_set() function. This can result in I2cap
connection or broadcast abnormality issue, possibly leading to denial
of service.

Fixed status
Not fixed yet.

CVE-2024-24859: Race condition bug in sniff_{min,max}_interval_set()
in bluetooth driver causes DoS

CVSS v3(NIST): N/A
CVSS v3(CNA): 4.6 (MEDIUM)

A race condition was found in the Linux kernel's net/bluetooth in
sniff_{min,max}_interval_set() function. This can result in a
bluetooth sniffing exception issue, possibly leading denial of
service.

Fixed status
Not fixed yet.

CVE-2024-24860: NULL pointer dereference bug was found in bluetooth
device driver in {min,max}_key_size_set()

CVSS v3(NIST): N/A
CVSS v3(CNA): 4.6 (MEDIUM)

A race condition was found in the Linux kernel's bluetooth device
driver in {min,max}_key_size_set() function. This can result in a null
pointer dereference issue, possibly leading to a kernel panic or
denial of service issue.

It looks like commit da9065caa ("Bluetooth: Fix atomicity violation in
{min,max}_key_size_set") fixes this vulnerability but accessing to the
bugzilla (https://bugzilla.openanolis.cn/show_bug.cgi?id=8151) is
restricted now so we need to wait for sometime.

Fixed status
Not fixed yet.

CVE-2024-24861: Race condition bug was found in media/xc4000 device
driver in xc4000 xc4000_get_frequency()

CVSS v3(NIST): N/A
CVSS v3(CNA): 3.3 (LOW)

A race condition was found in the Linux kernel's media/xc4000 device
driver in xc4000 xc4000_get_frequency() function. This can result in
return value overflow issue, possibly leading to malfunction or denial
of service issue.

Fixed status
Not fixed yet.

CVE-2024-24864: Race condition bug in media/dvb-core in dvbdmx_write()
causes DoS

A race condition was found in the Linux kernel's media/dvb-core in
dvbdmx_write() function. This can result in a null pointer dereference
issue, possibly leading to a kernel panic or denial of service issue.

CVSS v3(NIST): N/A
CVSS v3(CNA): 5.3 (MEDIUM)

Fixed status
Not fixed yet.

* Updated CVEs

CVE-2024-1086: netfilter: nf_tables: reject QUEUE/DROP verdict parameters

stable 6.1, 6.6, and 6.7 were fixed.

Fixed status
mainline: [f342de4e2f33e0e39165d8639387aa6c19dff660]
stable/6.1: [8e34430e33b8a80bc014f3efe29cac76bc30a4b4]
stable/6.6: [6653118b176a00915125521c6572ae8e507621db]
stable/6.7: [f05a497e7bc8851eeeb3a58da180ba469efebb05]

CVE-2024-23849: net/rds: Fix UBSAN: array-index-out-of-bounds in rds_cmsg_recv

The mainlinx, stable 6.1, 6.6, and 6.7 were fixed.

Fixed status
mainline: [13e788deb7348cc88df34bed736c3b3b9927ea52]
stable/6.1: [71024928b3f71ce4529426f8692943205c58d30b]
stable/6.6: [7a73190ea557e7f26914b0fe04c1f57a96cb771f]
stable/6.7: [0b787c2dea15e7a2828fa3a74a5447df4ed57711]

CVE-2024-23851: Kernel crash in drivers/md/dm-ioctl.c when allocate
memory more than INT_MAX bytes

Fixed in 6.8-rc3.

Fixed status
mainline: [bd504bcfec41a503b32054da5472904b404341a4]

Currently tracking CVEs

CVE-2021-31615: Unencrypted Bluetooth Low Energy baseband links in
Bluetooth Core Specifications 4.0 through 5.2

There is no fix information.

CVE-2020-26556: kernel: malleable commitment Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26557: kernel: predictable Authvalue in Bluetooth Mesh
Provisioning Leads to MITM

No fix information.

CVE-2020-26559: kernel: Authvalue leak in Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26560: kernel: impersonation attack in Bluetooth Mesh Provisioning

No fix information.

Regards,
-- 
Masami Ichikawa
Cybertrust Japan Co., Ltd.

Email :masami.ichikawa@cybertrust.co.jp
          :masami.ichikawa@miraclelinux.com


^ permalink raw reply	[flat|nested] 33+ messages in thread

* [kernel-cve-report] New CVE entries this week
@ 2024-01-31 23:18 Masami Ichikawa
  0 siblings, 0 replies; 33+ messages in thread
From: Masami Ichikawa @ 2024-01-31 23:18 UTC (permalink / raw)
  To: cip-dev

Hi!

It's this week's CVE report.

This week reported 10 new CVEs and 3 updated CVEs.

* New CVEs

CVE-2021-33630: net/sched: cbs: Fix not adding cbs instance to list

CVSS v3(NIST): N/A
CVSS v3(CNA): 5.5 (MEDIUM)

NULL Pointer Dereference vulnerability in openEuler kernel on Linux
(network modules) allows Pointer Manipulation. This vulnerability is
associated with program files net/sched/sch_cbs.C. This issue affects
openEuler kernel: from 4.19.90 before 4.19.90-2401.3.

It was introduced by commit e0a7683 ("net/sched: cbs: fix port_rate
miscalculation") in 5.2-rc1. This commit was backported to 4.19 so
that 4.19 is affected too.
This bug was fixed in 5.4-rc1.

Fixed status
mainline: [3e8b9bfa110896f95d602d8c98d5f9d67e41d78c]

CVE-2024-22099: NULL pointer dereference bug and buffer overflow
vulnerabilities was found in the bluetooth subsystem

CVSS v3(NIST): 5.5 (MEDIUM)
CVSS v3(CNA): 6.3 (MEDIUM)

NULL Pointer Dereference vulnerability in Linux Linux kernel kernel on
Linux, x86, ARM (net, bluetooth modules) allows Overflow Buffers. This
vulnerability is associated with program files
/net/bluetooth/rfcomm/core.C. This issue affects Linux kernel:
v2.6.12-rc2.

Fixed status
Not fixed yet

CVE-2024-23307: Integer Overflow bug was found md/raid/raid5 modules

CVSS v3(NIST): 7.8 (HIGH)
CVSS v3(CNA): 4.4 (MEDIUM)

Integer Overflow or Wraparound vulnerability in Linux Linux kernel
kernel on Linux, x86, ARM (md, raid, raid5 modules) allows Forced
Integer Overflow.

Fixed status
Not fixed yet

CVE-2024-0841: hugetlbfs: Null pointer dereference in
hugetlbfs_fill_super function

CVSS v3(NIST): N/A
CVSS v3(CNA): 6.6 (MEDIUM)

A null pointer dereference flaw was found in the hugetlbfs_fill_super
function in the Linux kernel hugetlbfs (HugeTLB pages) functionality.
This issue may allow a local user to crash the system or potentially
escalate their privileges on the system.

It seems as if all stable kernels are affected.

Fixed status
Not fixed yet

CVE-2023-52340: ipv6: remove max_size check inline with ipv4

CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

According to the Amazon Linux Security Center
(https://alas.aws.amazon.com/cve/html/CVE-2023-52340.html), it
describes following that.

When a router encounters an IPv6 packet too big to transmit to the
next-hop, it returns an ICMP6 "Packet Too Big" (PTB) message to the
sender. The sender caches this updated Maximum Transmission Unit (MTU)
so it knows not to exceed this value when subsequently routing to the
same host.
In Linux kernels prior to 6.3, garbage collection is run on the IPv6
Destination Route Cache if the number of entries exceeds a threshold
when adding the destination to the cache. This garbage collection
examines every entry in the cache while holding a lock. In these
affected kernel versions, a flood of the IPv6 ICMP6 PTB messages could
cause high lock contention and increased CPU usage, leading to a
Denial-of-Service.
The fix backports the garbage collection improvements from Linux
kernel 6.3 by bringing the IPv6 code closer to the IPv4 code, which
does not have this issue.

This bug was fixed by commit af6d103 ("ipv6: remove max_size check
inline with ipv4") in 6.3-rc1. The patch doesn't have a fixed-by tag
however, it looks as if 4.4 might be affected too.

Fixed status
mainline: [af6d10345ca76670c1b7c37799f0d5576ccef277]
stable/4.19: [95372b040ae689293c6863b90049f1af68410c8b]
stable/5.10: [dd56c5790dc3484f3c89fd4e21735c796a82b40d]
stable/5.15: [b8a5308feedda10d4875a912e2e1f6be215a4ead]
stable/5.4: [584756c3d75a1722a868a1d22602251385bee798]
stable/6.1: [0f22c8a6efe63c16d1abf1e6c0317abbf121f883]

CVE-2023-6200: A use-after-free bug causes arbitrary code execution
when processing ICMPv6 router advertisement packet

CVSS v3(NIST): N/A
CVSS v3(CNA): 7.5 (HIGH)

A race condition was found in the Linux Kernel. Under certain
conditions, an unauthenticated attacker from an adjacent network could
send an ICMPv6 router advertisement packet, causing arbitrary code
execution.

This bug was introduced by commit 3dec89b ("net/ipv6: Remove expired
routes with a separated list of routes") in 6.6-rc1. This commit is
not backported to older stable kernels.
It is fixed in 6.7-rc1.

Fixed status
mainline: [dade3f6a1e4e35a5ae916d5e78b3229ec34c78ec]
stable/6.6: [b577b9aa1340ee7f36441b0740691550abaad5f2]

CVE-2024-21803: A use-after-free bug was found in the bluetooth subsystem

CVSS v3(NIST): N/A
CVSS v3(CNA): 3.5 (LOW)

Use After Free vulnerability in Linux Linux kernel kernel on Linux,
x86, ARM (bluetooth modules) allows Local Execution of Code. This
vulnerability is associated with program files
https://gitee.Com/anolis/cloud-kernel/blob/devel-5.10/net/bluetooth/af_bluetooth.C.
This issue affects Linux kernel: from v2.6.12-rc2 before v6.8-rc1.

According to the CVE description, it was fixed in 6.8-rc1 but there is
no information about this fix.

Fixed status
No information

CVE-2024-0564: Kernel information leak bug was found in the KSM feature

CVSS v3(NIST): N/A
CVSS v3(CNA): 4.7 (MEDIUM)

A flaw was found in the Linux kernel's memory deduplication mechanism.
The max page sharing of Kernel Samepage Merging (KSM), added in Linux
kernel version 4.4.0-96.119, can create a side channel. When the
attacker and the victim share the same host and the default setting of
KSM is "max page sharing=256", it is possible for the attacker to time
the unmap to merge with the victim's page. The unmapping time depends
on whether it merges with the victim's page and additional physical
pages are created beyond the KSM's "max page share". Through these
operations, the attacker can leak the victim's page.

This bug was fixed by commit 2c653d0e ("ksm: introduce
ksm_max_page_sharing per page deduplication limit") in 4.13-rc1.

Ubuntu applied the following patch for xenial Linux 4.4.0-96.119 package.

ksm: introduce ksm_max_page_sharing per page deduplication limit:
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial/commit/?h=Ubuntu-4.4.0-96.119&id=731b565d8abadebb649c78fbb45983ecae7b1463


Fixed status
mainline: [2c653d0ee2ae78ff3a174cc877a057c8afac7069]

CVE-2024-1085: netfilter: nf_tables: check if catch-all set element is
active in next generation

CVSS v3(NIST): N/A
CVSS v3(CNA): 7.8 (HIGH)

A use-after-free vulnerability in the Linux kernel's netfilter:
nf_tables component can be exploited to achieve local privilege
escalation. The nft_setelem_catchall_deactivate() function checks
whether the catch-all set element is active in the current generation
instead of the next generation before freeing it, but only flags it
inactive in the next generation, making it possible to free the
element multiple times, leading to a double free vulnerability. We
recommend upgrading past commit
b1db244ffd041a49ecc9618e8feb6b5c1afcdaa7.

This bug was introduced by commit aaa3104 ("netfilter: nftables: add
catch-all set element support") in 5.13-rc1.
The commit aaa3104 is not backported to before 5.13 so that 5.10, 5.4,
and 4.x are not affected.
Fixed in 6.8-rc1.

Fixed status
mainline: [b1db244ffd041a49ecc9618e8feb6b5c1afcdaa7]
stable/5.15: [c9ed30eea4f7bfa2441235ce23abd339ee671f50]
stable/6.1: [a372f1d01bc11aa85773a02353cd01aaf16dc18e]
stable/6.6: [7baa33837ee2473eb0afd9755e29a25cd3771eac]
stable/6.7: [7e0f5f8ae3e5f17e367f7040ade7a467f1f0e3b9]

CVE-2024-1086: netfilter: nf_tables: reject QUEUE/DROP verdict parameters

CVSS v3(NIST): N/A
CVSS v3(CNA): 7.8 (HIGH)

A use-after-free vulnerability in the Linux kernel's netfilter:
nf_tables component can be exploited to achieve local privilege
escalation. The nft_verdict_init() function allows positive values as
drop error within the hook verdict, and hence the nf_hook_slow()
function can cause a double free vulnerability when NF_DROP is issued
with a drop error which resembles NF_ACCEPT. We recommend upgrading
past commit f342de4e2f33e0e39165d8639387aa6c19dff660.

This bug was introduced by commit e0abdad ("netfilter: nf_tables:
accept QUEUE/DROP verdict parameters") in 3.15-rc1. Fixed in 6.8r-c2.

Fixed status
mainline: [f342de4e2f33e0e39165d8639387aa6c19dff660]

* Updated CVEs

CVE-2023-46838: xen-netback: don''t produce zero-size SKB frags

All stable kernels were fixed.

Fixed status
stable/4.19: [5bb8270789c88c0e4ad78c0de2f274f2275c7f6c]
stable/5.10: [cce8ba6fa4ec43ad778d64823a2f8ca120d362c1]
stable/5.15: [e03023fcdb5e959d4252b3a38e1b27afb6c1c23c]
stable/5.4: [4404c2b832cf0a842b6e3c63fb5749e97dc618ea]
stable/6.1: [437360133cbd1e9fb88b122e84fff0df08f18e23]
stable/6.6: [78376d4415602d97773f20b49f4aa5fc8666f7a9]
stable/6.7: [0179c6b07f7ed2f3ea7309596169e15a59e7ee0e]


CVE-2023-6915: ida: Fix crash in ida_free when the bitmap is empty

stable 5.10, 5.15, and 5.4 were fixed.

Fixed status
mainline: [af73483f4e8b6f5c68c9aa63257bdd929a9c194a]
stable/5.10: [dbf8b0d9387fa02de0aa047ce23eb3a7bd134e03]
stable/5.15: [5dbcdaf4dbfe074e9142991c5c28eef789c1f6c6]
stable/5.4: [ef7152f8705fed11796641d7644acc3c950b5967]
stable/6.1: [9efdc0081ccae62c44a929e21d32bacc5f2e113f]
stable/6.6: [ffcaafdb8be64555e9928d943a3655c755dba92b]

CVE-2023-50431: habanalabs: fix information leak in sec_attest_info()

stable 6.1, 6.6, and 6.7 were fixed.

Fixed status
mainline: [a9f07790a4b2250f0140e9a61c7f842fd9b618c7]
stable/6.1: [6d98d249175e568f72ca94cbd6f959bc4476414e]
stable/6.6: [975aaaddc226303d382baa0d0ece84e8bec1fcf5]
stable/6.7: [db43f2eabdceedc41b8c3e0621ac42ca19b13b7d]

CVE-2023-5633: drm/vmwgfx: Keep a gem reference to user bos in surfaces

stable 6.1 was fixed.

Fixed status
mainline: [91398b413d03660fd5828f7b4abc64e884b98069]
stable/6.1: [104f95698cad038caa8f7496be67f738d8ace9cb]
stable/6.5: [1474b39f961703d0bb33833a6d6b112826839781]

Currently tracking CVEs

CVE-2021-31615: Unencrypted Bluetooth Low Energy baseband links in
Bluetooth Core Specifications 4.0 through 5.2

There is no fix information.

CVE-2020-26556: kernel: malleable commitment Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26557: kernel: predictable Authvalue in Bluetooth Mesh
Provisioning Leads to MITM

No fix information.

CVE-2020-26559: kernel: Authvalue leak in Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26560: kernel: impersonation attack in Bluetooth Mesh Provisioning

No fix information.

Regards,
-- 
Masami Ichikawa
Cybertrust Japan Co., Ltd.

Email :masami.ichikawa@cybertrust.co.jp
          :masami.ichikawa@miraclelinux.com


^ permalink raw reply	[flat|nested] 33+ messages in thread

* [kernel-cve-report] New CVE entries this week
@ 2024-01-24 23:17 Masami Ichikawa
  0 siblings, 0 replies; 33+ messages in thread
From: Masami Ichikawa @ 2024-01-24 23:17 UTC (permalink / raw)
  To: cip-dev

Hi!

It's this week's CVE report.

This week reported 12 new CVEs and 4 updated CVEs.

* New CVEs

CVE-2024-0639: A deadlock bug causes DoS in the SCTP subsystem

CVSS v3(NIST): 5.5 (MEDIUM)
CVSS v3(CNA): 4.7 (MEDIUM)

A denial of service vulnerability due to a deadlock was found in
sctp_auto_asconf_init in net/sctp/socket.c in the Linux kernel’s SCTP
subsystem.
This flaw allows guests with local user privileges to trigger a
deadlock and potentially crash the system.

Introduced by commit 34e5b01 ("sctp: delay auto_asconf init until
binding the first addr") in 5.13-rc1. Fixed in 6.5-rc1.
The commit 34e5b01 is not backported to 4.19 and 4.4 so these kernels
are not affected.

Fixed status
cip/4.4-st: [bda06654a7e8d5d572c4df906e888a00d5d9c8a1]
mainline: [6feb37b3b06e9049e20dcf7e23998f92c9c5be9a]
stable/4.19: [0ad0e8b0cb0e28626ab6dffe3da883941b9cbc4b]
stable/5.10: [6d2243ab783bf79d1d674ff0ca26229233c56508]
stable/5.15: [1fba2510b52f0bb9f408700e78db6d8d0ed6bcd5]
stable/5.4: [4d8fc6137749471ba0f64c9bc64e98113c015ed7]
stable/6.1: [1aa5a6a6d28c77e364feaba35ff7f12d2d74fec1]

CVE-2024-0641: A DoS vulnerability was found in the TIPC subsystem

CVSS v3(NIST): 5.5 (MEDIUM)
CVSS v3(CNA): 4.7 (MEDIUM)

A denial of service vulnerability was found in tipc_crypto_key_revoke
in net/tipc/crypto.c in the Linux kernel’s TIPC subsystem.
This flaw allows guests with local user privileges to trigger a
deadlock and potentially crash the system.

Introduced by commit fc1b6d6 ("tipc: introduce TIPC encryption &
authentication") in 5.5-rc1. Fixed in 6.6-rc5.

Fixed status
mainline: [08e50cf071847323414df0835109b6f3560d44f5]
stable/5.10: [6a24d0661fa389c241d935da38e0f6a5ee8eb1ae]
stable/5.15: [24fb22bddb71c6bfbe0fe25e1b7f793c5b580918]
stable/6.1: [143e72757a902abcecd5f487553f44dc19a56cfc]

CVE-2023-46838: Linux: netback processing of zero-length transmit fragment

CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Transmit requests in Xen's virtual network protocol can consist of
multiple parts.
While not really useful, except for the initial part any of them may
be of zero length,
i.e. carry no data at all.  Besides a certain initial portion of the
to be transferred data, these parts are
directly translated into what Linux calls SKB fragments.  Such
converted request parts can,
when for a particular SKB they are all of length zero, lead to a
de-reference of NULL in core networking code.

According to the commit log c7ec4f2d ("xen-netback: don't produce
zero-size SKB frags") it said that

"""
While frontends may submit zero-size requests (wasting a precious
slot), core networking code as of at least 3ece782
("sock: skb_copy_ubufs support for compound pages") can't deal with
SKBs when they have all zero-size fragments.
"""

the commit 3ece782 ("sock: skb_copy_ubufs support for compound pages")
is not back ported to Linux 4.4.

Fixed status
mainline: [c7ec4f2d684e17d69bbdd7c4324db0ef5daac26a]

CVE-2024-0775: A use-after-free bug was found in the ext4 file system

CVSS v3(NIST): N/A
CVSS v3(CNA): 6.7 (MEDIUM)

A use-after-free flaw was found in the __ext4_remount in
fs/ext4/super.c in ext4 in the Linux kernel. This flaw allows a local
user to cause
an information leak problem while freeing the old quota file names
before a potential failure, leading to a use-after-free.

It was fixed in 6.4-rc2.

Fixed status
cip/4.4-rt: [801ba552e9546571d60c628f98cd2db2301fca49]
mainline: [4c0b4818b1f636bc96359f7817a2d8bab6370162]
stable/4.19: [37302d4c2724dc92be5f90a3718eafa29834d586]
stable/5.10: [37c69da3adc45fc34df0b8d07a158a6fa5b2a3f7]
stable/5.15: [b2f1314e6e36e2322554e5e6e9598eedd349d942]
stable/5.4: [2dda2029067106f0835655a0417f1a5eaf3ba0b0]
stable/6.1: [25c9fca7b71c5045d6dc537430af5b2e79598fa1]

CVE-2023-46343: NULL pointer dereference bug was found in net/nfc/nci/spi.c

CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel before 6.5.9, there is a NULL pointer dereference
in send_acknowledge in net/nfc/nci/spi.c.

Introduced by commit 391d8a2 ("NFC: Add NCI over SPI receive") in
3.11-rc1. Fixed in 6.6-rc7.

Fixed status
cip/4.4-st: [bee47349504c09414e9602292a87af6fadc1a583]
mainline: [7937609cd387246aed994e81aa4fa951358fba41]
stable/4.19: [5622592f8f74ae3e594379af02e64ea84772d0dd]
stable/5.10: [c95fa5b20fe03609e0894656fa43c18045b5097e]
stable/5.15: [ffdc881f68073ff86bf21afb9bb954812e8278be]
stable/5.4: [76050b0cc5a72e0c7493287b7e18e1cb9e3c4612]
stable/6.1: [d7dbdbe3800a908eecd4975c31be47dd45e2104a]

CVE-2023-51042: A use-after-free bug was found in
drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c

CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel before 6.4.12, amdgpu_cs_wait_all_fences in
drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c has a fence use-after-free.
It was fixed in 6.5-rc1.

Fixed status
mainline: [2e54154b9f27262efd0cb4f903cc7d5ad1fe9628]
stable/4.19: [f9da11d96bde3db277f061ac5a665c234d505787]
stable/5.10: [b870b9a47fdba29bd6828f690e4817c950fa3430]
stable/5.15: [ef568da1fd843581e855c79a368209b752dea2c1]
stable/5.4: [c6059af6bf5ed436b4aa5229e8113bd2546322d4]
stable/6.1: [dd0b3b367c3839e439f36af908b39c98929a5e54]

CVE-2023-51043: A use-after-free bug was found in drivers/gpu/drm/drm_atomic.c

CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel before 6.4.5, drivers/gpu/drm/drm_atomic.c has a
use-after-free during a race condition between a nonblocking atomic
commit and a driver unload.
It seems as if it would be nice to call drm_dev_ref() in
drm_atomic_state_init() and call drm_dev_unref() in
drm_atomic_state_free() to put/get instance of dev in Linux 4.4.

It fixed in 6.5-rc3.

Fixed status
mainline: [4e076c73e4f6e90816b30fcd4a0d7ab365087255]
stable/4.19: [73a82b22963defa87204f0f9f44a534adf7f831a]
stable/5.10: [f09c0ac142c59495262dd80545f261b2aeeba538]
stable/5.15: [30580f3a3301173b1413a7b6d6ea100ec8c75da0]
stable/5.4: [380c7ceabdde0ea5b4e709620f299bcd5c1c8abc]
stable/6.1: [e4a0e09b79bd2c0895c508cdc5e0265a083cc05d]

CVE-2024-22705: ksmbd: fix slab-out-of-bounds in smb_strndup_from_utf16()

CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

An issue was discovered in ksmbd in the Linux kernel before 6.6.10.
smb2_get_data_area_len in fs/smb/server/smb2misc.c can cause an
smb_strndup_from_utf16 out-of-bounds access because the relationship
between Name data and CreateContexts data is mishandled.
It was fixed in 6.7-rc8.

Fixed status
mainline: [d10c77873ba1e9e6b91905018e29e196fd5f863d]
stable/5.15: [d739f2b6d8f57aa9377362cd8c0b1152a4dd6bd5]
stable/6.1: [7a3bbbadac4be9d30b45e9f1134e94294f79ce77]
stable/6.6: [7d5f219f1ef69f27eb8cbfb794d634fc9c4d24ac]

CVE-2024-23848: A use-after-free bug was found in
drivers/media/cec/core/cec-adap.c

CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In the Linux kernel through 6.7.1, there is a use-after-free in
cec_queue_msg_fh, related to drivers/media/cec/core/cec-adap.c and
drivers/media/cec/core/cec-api.c.

Fixed status
Not fixed yet.

CVE-2024-23849: An oob access bug was found in net/rds/af_rds.c

CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In rds_recv_track_latency in net/rds/af_rds.c in the Linux kernel
through 6.7.1, there is an off-by-one error for an
RDS_MSG_RX_DGRAM_TRACE_MAX comparison,
resulting in out-of-bounds access.

It was introduced by commit 3289025aedc0 ("RDS: add receive message
trace used by application") in 4.11-rc1.

Fixed status
Patch is in the netdev tre.

CVE-2024-23850: btrfs: do not ASSERT() if the newly created subvolume
already got read

CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

In btrfs_get_root_ref in fs/btrfs/disk-io.c in the Linux kernel
through 6.7.1, there can be an assertion failure and crash because a
subvolume can be read out too
soon after its root item is inserted upon subvolume creation.

It was introduced by commit 2dfb1e43f57d ("btrfs: preallocate anon
block device at first phase of snapshot creation") in 5.9-rc1.

Fixed status
Patch is available
(https://lore.kernel.org/all/6a80cb4b32af89787dadee728310e5e2ca85343f.1705741883.git.wqu%40suse.com/)
but it hasn't been merged yet.

CVE-2024-23851: Kernel crash in drivers/md/dm-ioctl.c when allocate
memory more than INT_MAX bytes

CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

copy_params in drivers/md/dm-ioctl.c in the Linux kernel through 6.7.1
can attempt to allocate more than INT_MAX bytes, and crash, because of
a missing
param_kernel->data_size check. This is related to ctl_ioctl.

Fixed status
Not fixed yet.

* Updated CVEs

CVE-2023-50431: habanalabs: fix information leak in sec_attest_info()

The mainline was fixed.

Fixed status
mainline: [a9f07790a4b2250f0140e9a61c7f842fd9b618c7]

CVE-2023-6915: ida: Fix crash in ida_free when the bitmap is empty

stable 6.1 and 6.6 are fixed.

Fixed status
mainline: [af73483f4e8b6f5c68c9aa63257bdd929a9c194a]
stable/6.1: [9efdc0081ccae62c44a929e21d32bacc5f2e113f]
stable/6.6: [ffcaafdb8be64555e9928d943a3655c755dba92b]

CVE-2023-6610: OOB Access in smb2_dump_detail

stable 6.1 and 6.6 are fixed.

Fixed status
mainline: [567320c46a60a3c39b69aa1df802d753817a3f86]
stable/6.1: [5411e3292792be7dafd1fe948a87e3ca29c1f550]
stable/6.6: [c5e0ed716c52fddea5e625668e75658c3b81d3fc]

CVE-2022-36402: An integer overflow vulnerability was found in vmwgfx driver

The mainline, 5.10, 5.15, and 6.1 are fixed.
This vulnerability was introduced by commit d80efd5 ("drm/vmwgfx:
Initial DX support") in 4.3-rc1.
It was fixed in 6.5.

Fixed status
mainline: [14abdfae508228a7307f7491b5c4215ae70c6542]
stable/5.10: [8735d1c66c7cf54e7b265a2911891f75674db342]
stable/5.15: [c8aab333d41a4ed6c5e7987c6cc5505ab86b5652]
stable/6.1: [115f2ccd3a998fe7247f59f8fb5feffc878bcbb7]

Currently tracking CVEs

CVE-2021-31615: Unencrypted Bluetooth Low Energy baseband links in
Bluetooth Core Specifications 4.0 through 5.2

There is no fix information.

CVE-2020-26556: kernel: malleable commitment Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26557: kernel: predictable Authvalue in Bluetooth Mesh
Provisioning Leads to MITM

No fix information.

CVE-2020-26559: kernel: Authvalue leak in Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26560: kernel: impersonation attack in Bluetooth Mesh Provisioning

No fix information.

Regards,
-- 
Masami Ichikawa
Cybertrust Japan Co., Ltd.

Email :masami.ichikawa@cybertrust.co.jp
          :masami.ichikawa@miraclelinux.com


^ permalink raw reply	[flat|nested] 33+ messages in thread

* [kernel-cve-report] New CVE entries this week
@ 2024-01-10 22:52 Masami Ichikawa
  0 siblings, 0 replies; 33+ messages in thread
From: Masami Ichikawa @ 2024-01-10 22:52 UTC (permalink / raw)
  To: cip-dev

Hi!

It's this week's CVE report.

This week reported 2 new CVEs and 4 updated CVEs.

* New CVEs

CVE-2023-6270: AoE: improper reference count leads to use-after-free
vulnerability

CVSS v3(NIST): N/A
CVSS v3(CNA): 7.0 (HIGH)

A flaw was found in the ATA over Ethernet (AoE) driver in the Linux
kernel. The aoecmd_cfg_pkts() function improperly updates the refcnt
on `struct net_device`, and a use-after-free can be triggered by
racing between the free on the struct and the access through the
`skbtxq` global queue. This could lead to a denial of service
condition or potential code execution.

Fixed status
Not fixed yet

CVE-2024-0228: netfilter: nf_tables: skip set commit for deleted/destroyed sets

This CVE was rejected because of a duplicate of CVE-2024-0193.

CVE-2024-0340: vhost: use kzalloc() instead of kmalloc() followed by memset()

CVSS v3(NIST): N/A
CVSS v3(CNA): 4.4 (MEDIUM)

A vulnerability was found in vhost_new_msg in drivers/vhost/vhost.c in
the Linux kernel, which does not properly initialize memory in
messages passed between virtual guests and the host operating system
in the vhost/vhost.c:vhost_new_msg() function. This issue can allow
local privileged users to read some kernel memory contents when
reading from the /dev/vhost-net device file.

The vhost_new_msg() was introduced by commit 6b1e6cc ("vhost: new
device IOTLB API ") in 4.8-rc1. The memset() was added by commit
670ae9c ("vhost: fix info leak due to uninitialized memory") in
4.18-rc1.
The vhost_new_msg() doesn't exist in Linux 4.4.

Fixed status
mainline: [4d8df0f5f79f747d75a7d356d9b9ea40a4e4c8a9]

* Updated CVEs

CVE-2023-1193: use-after-free in setup_async_work()

stable 6.1 was fixed.

Fixed status
mainline: [3a9b557f44ea8f216aab515a7db20e23f0eb51b9]
stable/5.15: [9494242c8e76e6a98c8ab5f6aed0fa4bd56ac6d5]
stable/6.1: [8d271ef5e5cac8a470076891b248a28a2c57fb1e]

CVE-2023-51779: Bluetooth: af_bluetooth: Fix Use-After-Free in bt_sock_recvmsg

stable 5.10 and 5.15 were fixed.

Fixed status
mainline: [2e07e8348ea454615e268222ae3fc240421be768]
stable/5.10: [db1b14eec8c61a20374de9f9c2ddc6c9406a8c42]
stable/5.15: [2b16d960c79abc397f102c3d23d30005b68cb036]
stable/6.1: [37f71e2c9f515834841826f4eb68ec33cfb2a1ff]
stable/6.6: [1d576c3a5af850bf11fbd103f9ba11aa6d6061fb]

CVE-2023-6606: Out-Of-Bounds Read vulnerability in smbCalcSize

stable 4.19, 5.4, 5.10 and 5.15 were fixed.

Fixed status
mainline: [b35858b3786ddbb56e1c35138ba25d6adf8d0bef]
stable/4.19: [89b6ae907c6bcc175bc95a67d6936217530a29ff]
stable/5.10: [0c54b79d1d9b25f5a406bcf1969f956e14c4704d]
stable/5.15: [ded3cfdefec8b2accc767f176419316b61c157c3]
stable/5.4: [508e2fdd978e4c26798eac2059f9520255904f82]
stable/6.1: [c60e10d1549f8748a68ec13dcd177c62843985ff]
stable/6.6: [ac48fcef5ec2e9ac85c0b39045d874e60eac75d7]


CVE-2024-0193: netfilter: nf_tables: skip set commit for deleted/destroyed sets

The mainline, stable 5.10, 5.15, 6.1, and 6.6 were fixed.

Fixed status
mainline: [7315dc1e122c85ffdfc8defffbb8f8b616c2eb1a]
stable/5.10: [73117ea03363d4493bd4e9f82f29b34b92d88a91]
stable/5.15: [d10f7540c5541ad9f4fe2a02a73153d25d4a540d]
stable/6.1: [0105571f80edb96f81bb4bbdd5233a9130dc345b]
stable/6.6: [b7f1c01b55ad2a5da12f08e5ec3c76dabb99882a]

Currently tracking CVEs

CVE-2021-31615: Unencrypted Bluetooth Low Energy baseband links in
Bluetooth Core Specifications 4.0 through 5.2

There is no fix information.

CVE-2020-26556: kernel: malleable commitment Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26557: kernel: predictable Authvalue in Bluetooth Mesh
Provisioning Leads to MITM

No fix information.

CVE-2020-26559: kernel: Authvalue leak in Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26560: kernel: impersonation attack in Bluetooth Mesh Provisioning

No fix information.

Regards,
-- 
Masami Ichikawa
Cybertrust Japan Co., Ltd.

Email :masami.ichikawa@cybertrust.co.jp
          :masami.ichikawa@miraclelinux.com


^ permalink raw reply	[flat|nested] 33+ messages in thread

* [kernel-cve-report] New CVE entries this week
@ 2024-01-03 23:09 Masami Ichikawa
  0 siblings, 0 replies; 33+ messages in thread
From: Masami Ichikawa @ 2024-01-03 23:09 UTC (permalink / raw)
  To: cip-dev

Hi!

It's this week's CVE report.

This week reported 4 new CVEs and 2 updated CVEs.

* New CVEs

CVE-2023-6531: io_uring/af_unix: disable sending io_uring over sockets

CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

A use-after-free bug was found in the io_uring subsystem for
supporting af_unix socket. There was a race condition bug that causes
use-after-free.

This bug was introduced by commit 0091bfc ("io_uring/af_unix: defer
registered files gc to io_uring release") in 6.1-rc1. It has been
backported to 5.4, 5.10, and 5.15.

Fixed status
mainline: [705318a99a138c29a512a72c3e0043b3cd7f55f4,
69db702c83874fbaa2a51af761e35a8e5a593b95]
stable/5.10: [3fe1ea5f921bf5b71cbfdc4469fb96c05936610e]
stable/6.1: [5a33d385eb36991a91e3dddb189d8679e2aac2be]

CVE-2023-6546: A use-after-free bug was found in the gsm_cleanup_mux()

CVSS v3(NIST): 7.0 (HIGH)
CVSS v3(CNA): 7.8 (HIGH)

A race condition was found in the GSM 0710 tty multiplexor in the
Linux kernel. This issue occurs when two threads execute the
GSMIOC_SETCONF ioctl on the same tty file descriptor with the gsm line
discipline enabled, and can lead to a use-after-free problem on a
struct gsm_dlci while restarting the gsm mux. This could allow a local
unprivileged user to escalate their privileges on the system.

In commit 9b9c819 ("tty: n_gsm: fix UAF in gsm_cleanup_mux") tried to
fix a use-after-free bug but introduced a race condition which causes
this use-after-free bug.

The commit 9b9c819 was introduced in 6.5.-rc4. This CVE was fixed in 6.5-rc7.

Fixed status
mainline: [3c4f8333b582487a2d1e02171f1465531cde53e3]
stable/5.10: [869ce5e5984595bd2c62b598d977debc218b6f4d]
stable/5.15: [2a523446438376bb7c224f3169ae9b98ce0fb893]
stable/6.1: [31311a9a4baae0ad47c85e448af21b2120344ff0]

CVE-2023-7192: A memory leak problem was found in
ctnetlink_create_conntrack() in the netfilter subsystem

CVSS v3(NIST): N/A
CVSS v3(CNA): 6.1 (MEDIUM)

A memory leak problem was found in ctnetlink_create_conntrack in
net/netfilter/nf_conntrack_netlink.c in the Linux Kernel. This issue
may allow a local attacker with CAP_NET_ADMIN privileges to cause a
denial of service (DoS) attack due to a refcount overflow.

This bug was introduced by commit 7d367e0 ("netfilter: ctnetlink: fix
soft lockup when netlink adds new entries (v2)") in 3.3-rc6.
The commit 7d367e0 fixes a race condition bug which was introduced by
commit cfed7e1 ("netfilter: nf_tables: add set garbage collection
helpers") in 4.1-rc1.

This CVE was fixed in 6.3-rc1.

Fixed status
cip/4.4: [a3f90f806278532e352739f354ace32e69e96da4]
cip/4.4-rt: [a3f90f806278532e352739f354ace32e69e96da4]
cip/4.4-st: [a3f90f806278532e352739f354ace32e69e96da4]
mainline: [ac4893980bbe79ce383daf9a0885666a30fe4c83]
stable/4.14: [8df5f3b50d9ce523251edf9cd0470963be20004b]
stable/4.19: [43b9a9c78e37a5532c2a9260dff9d9989f2bbb23]
stable/5.10: [1ff0b87df98b93e10ced45773aa7d35377355421]
stable/5.15: [af41b3cd9a9245f482b8855bd3c62c6f04ae68ab]
stable/5.4: [5d0d38805d3234ca2cd6fbeb74d706348f4bbc43]
stable/6.1: [4f25d1dff80535f088b8f8568dd731fb098e29b4]

CVE-2024-0193: netfilter: nf_tables: skip set commit for deleted/destroyed sets

CVSS v3(NIST): N/A
CVSS v3(CNA): 7.8 (HIGH)

A use-after-free flaw was found in the netfilter subsystem of the
Linux kernel. If the catchall element is garbage-collected when the
pipapo set is removed, the element can be deactivated twice. This can
cause a use-after-free issue on an NFT_CHAIN object or NFT_OBJECT
object, allowing a local unprivileged user to escalate their
privileges on the system.

This bug was introduced by commit 5f68718b34a5 ("netfilter: nf_tables:
GC transaction API to avoid race with control plane") in 6.5-rc6.
The commit 5f68718b34a5 was backported to 5.10, 5.15, 5.4, and 6.4.

Fixed status
Patch is merged into netfilter tree
(https://git.kernel.org/pub/scm/linux/kernel/git/netfilter/nf.git/commit/?id=7315dc1e122c85ffdfc8defffbb8f8b616c2eb1a)
but it hasn't been merged into the mainline yet.

* Updated CVEs

CVE-2023-51779: Bluetooth: af_bluetooth: Fix Use-After-Free in bt_sock_recvmsg

Stable 6.1 and 6.6 were fixed.

Fixed status
mainline: [2e07e8348ea454615e268222ae3fc240421be768]
stable/6.1: [37f71e2c9f515834841826f4eb68ec33cfb2a1ff]
stable/6.6: [1d576c3a5af850bf11fbd103f9ba11aa6d6061fb]

CVE-2023-6606: Out-Of-Bounds Read vulnerability in smbCalcSize

Stable 6.1 and 6.6 were fixed.

Fixed status
mainline: [b35858b3786ddbb56e1c35138ba25d6adf8d0bef]
stable/6.1: [c60e10d1549f8748a68ec13dcd177c62843985ff]
stable/6.6: [ac48fcef5ec2e9ac85c0b39045d874e60eac75d7]

Currently tracking CVEs

CVE-2021-31615: Unencrypted Bluetooth Low Energy baseband links in
Bluetooth Core Specifications 4.0 through 5.2

There is no fix information.

CVE-2020-26556: kernel: malleable commitment Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26557: kernel: predictable Authvalue in Bluetooth Mesh
Provisioning Leads to MITM

No fix information.

CVE-2020-26559: kernel: Authvalue leak in Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26560: kernel: impersonation attack in Bluetooth Mesh Provisioning

No fix information.

Regards,
-- 
Masami Ichikawa
Cybertrust Japan Co., Ltd.

Email :masami.ichikawa@cybertrust.co.jp
          :masami.ichikawa@miraclelinux.com


^ permalink raw reply	[flat|nested] 33+ messages in thread

* [kernel-cve-report] New CVE entries this week
@ 2023-12-27 22:47 Masami Ichikawa
  0 siblings, 0 replies; 33+ messages in thread
From: Masami Ichikawa @ 2023-12-27 22:47 UTC (permalink / raw)
  To: cip-dev

Hi!

It's this week's CVE report.

This week reported 5 new CVEs and 16 updated CVEs.

There was a big change in the ksmbd sub system in 5.15 that backported
lots of patches between 5.16 and 6.7-rc5 kernel to 5.15.
https://lore.kernel.org/stable/2023122045-snuggle-rocky-b3f8@gregkh/T/#t

This patchset fixes the following CVEs.
CVE-2022-47490, CVE-2023-1193, CVE-2023-1194, CVE-2023-32247, CVE-2023-32250
CVE-2023-32252, CVE-2023-32254, CVE-2023-32257, CVE-2023-32258, CVE-2023-38427
CVE-2023-38430, CVE-2023-38431, CVE-2023-3867

* New CVEs

CVE-2023-7042: wifi: ath10k: fix NULL pointer dereference in
ath10k_wmi_tlv_op_pull_mgmt_tx_compl_ev()

CVSS v3(NIST): N/A
CVSS v3(CNA): 4.4 (MEDIUM)

A null pointer dereference vulnerability was found in
ath10k_wmi_tlv_op_pull_mgmt_tx_compl_ev() in
drivers/net/wireless/ath/ath10k/wmi-tlv.c in the Linux kernel. This
issue could be exploited to trigger a denial of service.

This bug was introduced by commit dc405152bb64 ("ath10k: handle mgmt
tx completion event") in 4.19-rc1.

Fixed status
Patch has been merged into ath-next branch.

CVE-2023-51779: Bluetooth: af_bluetooth: Fix Use-After-Free in bt_sock_recvmsg

CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

bt_sock_recvmsg in net/bluetooth/af_bluetooth.c in the Linux kernel
through 6.6.8 has a use-after-free because of a bt_sock_ioctl race
condition.
This bug was introduced in less than or equal to 2.6.12-rc2.

Fixed status
mainline: [2e07e8348ea454615e268222ae3fc240421be768]

CVE-2023-51780: atm: Fix Use-After-Free in do_vcc_ioctl

CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

An issue was discovered in the Linux kernel before 6.6.8. do_vcc_ioctl
in net/atm/ioctl.c has a use-after-free because of a vcc_recvmsg race
condition.
This bug was introduced in less than or equal to 2.6.12-rc2.

Fixed status
mainline: [24e90b9e34f9e039f56b5f25f6e6eb92cdd8f4b3]
stable/4.14: [3ddeb55deec5e0e324d0ab8cc2ddd528518ea12d]
stable/4.19: [bff7ddb0d9d515170dcf133d239dba87c47c8cdb]
stable/5.10: [64a032015c336ca1795b3e1b1d1f94085ada3553]
stable/5.15: [3bb41dc361bfd938041a1d17a3768aa788a36a3c]
stable/5.4: [b099c28847cfa33854731eeec9c64619d99a1255]
stable/6.1: [2de2a6cbe14f7e949da59bddd5d69baf5dd893c0]
stable/6.6: [531fd46f92895bcdc41bedd12533266c397196da]

CVE-2023-51781: appletalk: Fix Use-After-Free in atalk_ioctl

CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

An issue was discovered in the Linux kernel before 6.6.8. atalk_ioctl
in net/appletalk/ddp.c has a use-after-free because of an
atalk_recvmsg race condition.
This bug was introduced in less than or equal to 2.6.12-rc2.

Fixed status
mainline: [189ff16722ee36ced4d2a2469d4ab65a8fee4198]
stable/4.14: [0686da1ada51c787610185de6289d8a5006ad263]
stable/4.19: [580ff9f59ab6537d8ce1d0d9f012cf970553ef3d]
stable/5.10: [a232eb81c7cb5d4dbd325d4611ed029b7fa07596]
stable/5.15: [5b87ac25e8cfeb2d3d27574cdc077b09e8ceca82]
stable/5.4: [9112bd107208cd6a4f0175ca36289ed170622cce]
stable/6.1: [1646b2929d5efc3861139ba58556b0f149c848f6]
stable/6.6: [e15ded324a3911358e8541a1b573665f99f216ef]

CVE-2023-51782: net/rose: Fix Use-After-Free in rose_ioctl

CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

An issue was discovered in the Linux kernel before 6.6.8. rose_ioctl
in net/rose/af_rose.c has a use-after-free because of a rose_accept
race condition.
This bug was introduced in less than or equal to 2.6.12-rc2.

Fixed status
mainline: [810c38a369a0a0ce625b5c12169abce1dd9ccd53]
stable/4.14: [02af3c8ab5cda2633b187bd18b5dc2b9f0af0859]
stable/4.19: [6c9afea8827dde62c4062185d22ac035090ba39b]
stable/5.10: [7eda5960a5332654b10d951e735750ed60d7f0a9]
stable/5.15: [3f1f6a94d8858706863fe90da35663f6e24be274]
stable/5.4: [3df812627e7d0bf557f3781c3448d42c8fe8313e]
stable/6.1: [01540ee2366a0a8671c35cd57a66bf0817106ffa]
stable/6.6: [63caa51833e8701248a8a89d83effe96f30e4c80]

* Updated CVEs

CVE-2023-6606: Out-Of-Bounds Read vulnerability in smbCalcSize

Fixed in the mainline.

Fixed status
mainline: [b35858b3786ddbb56e1c35138ba25d6adf8d0bef]

CVE-2023-6610: OOB Access in smb2_dump_detail

Fixed in the mainline.

Fixed status
mainline: [567320c46a60a3c39b69aa1df802d753817a3f86]

CVE-2022-47940: Linux Kernel ksmbd Out-Of-Bounds Read Information
Disclosure Vulnerability

stable/5.15 was fixed.

Fixed status
mainline: [158a66b245739e15858de42c0ba60fcf3de9b8e6]
stable/5.15: [6bb4399303383c2c06bce33f2335c39fbf35d979]

CVE-2023-1193: use-after-free in setup_async_work()

stable/5.15 was fixed.

Fixed status
mainline: [3a9b557f44ea8f216aab515a7db20e23f0eb51b9]
stable/5.15: [9494242c8e76e6a98c8ab5f6aed0fa4bd56ac6d5]

CVE-2023-1194: use-after-free in parse_lease_state()

stable/5.15 was fixed.

Fixed status
mainline: [fc6c6a3c324c1b3e93a03d0cfa3749c781f23de0]
stable/5.15: [55ceeb4e1c71793e852c20ad01ffd31515303546]
stable/6.1: [8f2984233c87a1d08f4c45f077130590c7a2c991]

CVE-2023-32247: Linux Kernel ksmbd Session Setup Memory Exhaustion
Denial-of-Service Vulnerability

stable/5.15 was fixed.

Fixed status
mainline: [ea174a91893956450510945a0c5d1a10b5323656]
stable/5.15: [a6a9601ba995d0fec635324cb9fd8d14f9bea14e]
stable/6.1: [1fc8a2b14ef5223f8e0b95faba2ee0a6e4d0f99d]
stable/6.3: [6775ee7ef4b37c521aa4cf3730f54554c4875542]

CVE-2023-32250: ksmbd: fix racy issue from session setup and logoff

stable/5.15 was fixed.

Fixed status
mainline: [f5c779b7ddbda30866cf2a27c63e34158f858c73]
stable/5.15: [708c304b583d789957399dd8237f212cf8ad1e4d]
stable/6.1: [f623f627ad2b1dc215ab3b0df53fb05cfd3a1c3b]
stable/6.3: [02f41d88f15d6b7d523e52cc3f87488f57e9265b]

CVE-2023-32252: Linux Kernel ksmbd Session NULL Pointer Dereference
Denial-of-Service Vulnerability

stable/5.15 was fixed.

Fixed status
mainline: [f5c779b7ddbda30866cf2a27c63e34158f858c73]
stable/5.15: [708c304b583d789957399dd8237f212cf8ad1e4d]
stable/6.1: [f623f627ad2b1dc215ab3b0df53fb05cfd3a1c3b]
stable/6.3: [02f41d88f15d6b7d523e52cc3f87488f57e9265b]

CVE-2023-32254: ksmbd: fix racy issue under cocurrent smb2 tree disconnect

stable/5.15 was fixed.

Fixed status
mainline: [30210947a343b6b3ca13adc9bfc88e1543e16dd5]
stable/5.15: [b36295c17fb97424406f0c3ab321b1ccaabb9be8]
stable/6.1: [bd80d35725a0cf4df9307bfe2f1a3b2cb983d8e6]
stable/6.3: [39366b47a59d46af15ac57beb0996268bf911f6a]

CVE-2023-32257: Linux Kernel ksmbd Session Race Condition Remote Code
Execution Vulnerability

stable/5.15 was fixed.

Fixed status
mainline: [f5c779b7ddbda30866cf2a27c63e34158f858c73]
stable/5.15: [708c304b583d789957399dd8237f212cf8ad1e4d]
stable/6.1: [f623f627ad2b1dc215ab3b0df53fb05cfd3a1c3b]
stable/6.3: [02f41d88f15d6b7d523e52cc3f87488f57e9265b]

CVE-2023-32258: Linux Kernel ksmbd Session Race Condition Remote Code
Execution Vulnerability

stable/5.15 was fixed.

Fixed status
mainline: [abcc506a9a71976a8b4c9bf3ee6efd13229c1e19]
stable/5.15: [ae06b798f72d6cc792cfa1745490be65da90eb03]
stable/6.1: [4aba9ab6a007e41182454f84f95c0bddf7d6d7e1]
stable/6.3: [920d5dd2d041484bf001c9713c2e3bcc6de79726]

CVE-2023-38427: OOB read bug was found in deassemble_neg_contexts()

stable/5.15 was fixed.

Fixed status
mainline: [f1a411873c85b642f13b01f21b534c2bab81fc1b]
stable/5.15: [4adb4fbd74812aeada97e7cc6de3dad41952443e]
stable/6.1: [bf12d7fb63b365fb766655cedcb5d5f292b0c35e]

CVE-2023-38430: OOB read bug was found in the ksmbd subsystem

stable/5.15 was fixed.

Fixed status
mainline: [1c1bcf2d3ea061613119b534f57507c377df20f9]
stable/5.15: [0d1a3f97efbe73fe6d6c18574e6ac94cd2492c11]
stable/6.1: [e01fc7caac9ce9ad76df9f42f7f61ef4bf1d27c9]

CVE-2023-38431: OOB read bug was found in the ksmbd subsystem

stable/5.15 was fixed.

Fixed status
mainline: [368ba06881c395f1c9a7ba22203cf8d78b4addc0]
stable/5.15: [df3a4518aee64f21bcafa891105b468413f27431]
stable/6.1: [543c12c2644e772caa6880662c2a852cfdc5a10c]

CVE-2023-3867: ksmbd: add missing compound request handing in some commands

stable/5.15 was fixed.

Fixed status
mainline: [7b7d709ef7cf285309157fb94c33f625dd22c5e1]
stable/5.15: [97f5c1e3086c8ba1473c265d9a5523cc9ef5579e]
stable/6.1: [869ef4f2965bbb91157dad220133f76c16faba9b]
stable/6.4: [ffaa0c85edd9245594a94918c09db9163b71767a]

CVE-2023-6679: dpll: sanitize possible null pointer dereference in
dpll_pin_parent_pin_set()

Fixed in the mainline.

Fixed status
mainline: [65c95f78917ea6fa7ff189a2c19879c4fe161873]

Currently tracking CVEs

CVE-2021-31615: Unencrypted Bluetooth Low Energy baseband links in
Bluetooth Core Specifications 4.0 through 5.2

There is no fix information.

CVE-2020-26556: kernel: malleable commitment Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26557: kernel: predictable Authvalue in Bluetooth Mesh
Provisioning Leads to MITM

No fix information.

CVE-2020-26559: kernel: Authvalue leak in Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26560: kernel: impersonation attack in Bluetooth Mesh Provisioning

No fix information.

Regards,
-- 
Masami Ichikawa
Cybertrust Japan Co., Ltd.

Email :masami.ichikawa@cybertrust.co.jp
          :masami.ichikawa@miraclelinux.com


^ permalink raw reply	[flat|nested] 33+ messages in thread

* [kernel-cve-report] New CVE entries this week
@ 2023-12-20 23:08 Masami Ichikawa
  0 siblings, 0 replies; 33+ messages in thread
From: Masami Ichikawa @ 2023-12-20 23:08 UTC (permalink / raw)
  To: cip-dev

Hi!

It's this week's CVE report.

This week reported 3 new CVEs and 1 updated CVEs.

Talking about CVE-2020-26555, additional mitigation patches were
merged into the mainline.
- Cover letter
https://lore.kernel.org/lkml/20231001084934.GA16906@linux-691t/T/#u

-Bluetooth: Reject connection with the device which has same BD_ADDR
https://github.com/torvalds/linux/commit/1ffc6f8cc33268731fcf9629fc4438f6db1191fc

- Bluetooth: hci_event: Ignore NULL link key
https://github.com/torvalds/linux/commit/33155c4aae5260475def6f7438e4e35564f4f3ba

* New CVEs

CVE-2023-6817: nft_set_pipapo: skip inactive elements during set walk

CVSS v3(NIST): N/A
CVSS v3(CNA): 7.8 (HIGH)

System may crash when walking through active elements in the
nft_pipapo_walk() in net/netfilter/nft_set_pipapo.c. During iteration,
an element can be deactivate twice so if accessing deactivated
element, it will cause a crash.

This bug was introduced by commit 3c4287f ("nf_tables: Add set type
for arbitrary concatenation of ranges") in 5.6-rc1. Before 5.6 kernels
are not affected.

Fixed status
mainline: [317eb9685095678f2c9f5a8189de698c5354316a]
stable/5.10: [bf72b44fe81be08a9fcd58aabf417cd3337ffc99]
stable/5.15: [e65128616faa101b336e52fefbd62b83bb309916]
stable/6.1: [189c2a82933c67ad360c421258d5449f6647544a]
stable/6.6: [c66d39f18e0ef16bac8c8491b657051f531a1eba]

CVE-2023-6931: perf: Fix perf_event_validate_size()

CVSS v3(NIST): N/A
CVSS v3(CNA): 7.8 (HIGH)

A heap out-of-bounds write vulnerability in the Linux kernel's
Performance Events system component can be exploited to achieve local
privilege escalation. A perf_event's read_size can overflow, leading
to an heap out-of-bounds increment or write in perf_read_group().

It was introduced by commit a723968 ("perf: Fix u16 overflows") in
4.3-rc1. Fixed in 6.7-rc5.

Fixed status
mainline: [382c27f4ed28f803b1f1473ac2d8db0afc795a1b]
stable/4.19: [f5d6ab016792c9d6d5280fdb7f8962eb3b8c620e]
stable/5.10: [208dd116f96ea19e5d38d7b80fce49bc5ce1bbe8]
stable/5.15: [ebc7597ce9719d2ff72e13df072680aa491f27fb]
stable/5.4: [152f51d159f35b2f64d7046429703500375becc9]
stable/6.1: [06dec254c59afd01b7a44838cf8bfc382bef019b]
stable/6.6: [cfe9295db0932f1b8e0d94ffc75521898e5a5a8a]

CVE-2023-6932: ipv4: igmp: fix refcnt uaf issue when receiving igmp query packet

CVSS v3(NIST): N/A
CVSS v3(CNA): 7.8 (HIGH)

A use-after-free vulnerability in the Linux kernel's ipv4: igmp
component can be exploited to achieve local privilege escalation. A
race condition can be exploited to cause a timer be mistakenly
registered on a RCU read locked object which is freed by another
thread.

This bug was introduced in less or equal to 2.6.12. Fixed in 6.7-rc4.

Fixed status
mainline: [e2b706c691905fe78468c361aaabc719d0a496f1]
stable/4.14: [be70b329c7fcb4a90c33546dc7c34bff07975b60]
stable/4.19: [6b6f5c6671fdfde9c94efe6409fa9f39436017e7]
stable/5.10: [772fe1da9a8d4dcd8993abaecbde04789c52a4c2]
stable/5.15: [c4a00c47a140c39a0497a40b0f54cf4586a2b1d7]
stable/5.4: [7ccf772a8bad7962d12d48723447c3605a6e23c1]
stable/6.1: [94445d9583079e0ccc5dde1370076ff24800d86e]
stable/6.6: [bf8601dabed0c134a7d58085824e3e466840c5d1]

* Updated CVEs

CVE-2023-25775: improper access control flaw in RDMA driver

stable/5.15 was fixed.

Fixed status
mainline: [bb6d73d9add68ad270888db327514384dfa44958]
stable/4.14: [92f871191e0bcb35dff37815579f15cac329955c]
stable/4.19: [f3c2760510c119c609e751c5a0b06cec6ae4bb4d]
stable/5.10: [ac65f8979b0eaac80c4710729c509d8837d8fdb7]
stable/5.15: [410c05b60c1af650b37ae45010086091f2d0cebe]
stable/5.4: [518b7f7d87aa87cf5173a937baa9a93fc6ed3d6d]
stable/6.1: [f01cfec8d3456bf389918eb898eda11f46d8b1b7]
stable/6.4: [ceba966f1d6391800cab3c1c9ac1661b5166bc5b]
stable/6.5: [782c5702b933477b088e80e6d07b9493145b2916]

Currently tracking CVEs

CVE-2021-31615: Unencrypted Bluetooth Low Energy baseband links in
Bluetooth Core Specifications 4.0 through 5.2

There is no fix information.

CVE-2020-26556: kernel: malleable commitment Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26557: kernel: predictable Authvalue in Bluetooth Mesh
Provisioning Leads to MITM

No fix information.

CVE-2020-26559: kernel: Authvalue leak in Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26560: kernel: impersonation attack in Bluetooth Mesh Provisioning

No fix information.

Regards,
-- 
Masami Ichikawa
Cybertrust Japan Co., Ltd.

Email :masami.ichikawa@cybertrust.co.jp
          :masami.ichikawa@miraclelinux.com


^ permalink raw reply	[flat|nested] 33+ messages in thread

* [kernel-cve-report] New CVE entries this week
@ 2023-12-13 22:52 Masami Ichikawa
  0 siblings, 0 replies; 33+ messages in thread
From: Masami Ichikawa @ 2023-12-13 22:52 UTC (permalink / raw)
  To: cip-dev

Hi!

It's this week's CVE report.

This week reported 9 new CVEs and 3 updated CVEs.

* New CVEs

CVE-2023-6560: io_uring out of boundary memory access in __io_uaddr_map()

CVSS v3(NIST): N/A
CVSS v3(CNA): 5.5 (MEDIUM)

An oob access vulnerability was found in the io_uring subsystem. There
is incorrect mapped page check when pages are not continuous. The
check logic checks the first and last page so if pages are not
continuous,  it results will do out of boundaries memory access.

This bug was introduced by commit 03d89a2 ("io_uring: support for user
allocated memory for rings/sqes") in 6.5-rc1.
It has been fixed in 6.7-rc4. The commit 03d89a2 is not backported to
stable kernels.

Fixed status
mainline: [820d070feb668aab5bc9413c285a1dda2a70e076]
stable/6.6: [4be625ba36bcfdfb9c72b712acd4ef943a269ebb]

CVE-2023-6606: Out-Of-Bounds Read vulnerability in smbCalcSize

CVSS v3(NIST): N/A
CVSS v3(CNA): 7.1 (HIGH)

An out-of-bounds read vulnerability was found in smbCalcSize in
fs/smb/client/netmisc.c in the Linux Kernel. This issue could allow a
local attacker to crash the system or leak internal kernel
information.

Fixed status
Not fixed yet.

CVE-2023-6610: OOB Access in smb2_dump_detail

CVSS v3(NIST): N/A
CVSS v3(CNA): 7.1 (HIGH)

An out-of-bounds read vulnerability was found in smb2_dump_detail in
fs/smb/client/smb2ops.c in the Linux Kernel. This issue could allow a
local attacker to crash the system or leak internal kernel
information.

Fixed status
Not fixed yet.

CVE-2023-6622: netfilter: nf_tables: bail out on mismatching dynset
and set expressions

CVSS v3(NIST): N/A
CVSS v3(CNA): 5.5 (MEDIUM)

A null pointer dereference vulnerability was found in
nft_dynset_init() in net/netfilter/nft_dynset.c in nf_tables in the
Linux kernel. This issue may allow a local attacker with CAP_NET_ADMIN
user privilege to trigger a denial of service.

This bug was introduced by commit 48b0ae0 ("netfilter: nftables:
netlink support for several set element expressions") in 5.11-rc1 so
prior to 5.11 kernels are not affected.

Fixed status
mainline: [3701cd390fd731ee7ae8b8006246c8db82c72bea]
stable/5.15: [cf5f113c41eb2c7dbe19d849a0883f7a429fa54b]
stable/6.1: [96f8654b701f772af5f358b91807ce2836ff3444]
stable/6.6: [5eeba00a89c5c6be4e45b69bef20d1d1b9edb968]

CVE-2023-50431: habanalabs: fix information leak in sec_attest_info()

CVSS v3(NIST): 5.5 (MEDIUM)
CVSS v3(CNA): N/A

sec_attest_info in drivers/accel/habanalabs/common/habanalabs_ioctl.c
in the Linux kernel through 6.6.5 allows an information leak to user
space because info->pad0 is not initialized.

Patch is available on the dri-devel list
(https://lists.freedesktop.org/archives/dri-devel/2023-November/431772.html)
but it hasn't been merged into the mainline yet.

Fixed status
Not fixed yet.

CVE-2023-6679: dpll: sanitize possible null pointer dereference in
dpll_pin_parent_pin_set()

CVSS v3(NIST): 5.5 (MEDIUM)
CVSS v3(CNA): 4.4 (MEDIUM)

A null pointer dereference vulnerability was found in
dpll_pin_parent_pin_set() in drivers/dpll/dpll_netlink.c in the
Digital Phase Locked Loop (DPLL) subsystem in the Linux kernel. This
issue could be exploited to trigger a denial of service.

Patch is available on the netdev mailing list
(https://lore.kernel.org/netdev/20231211083758.1082853-1-jiri@resnulli.us/)
but it hasn't been merged yet.
This bug was introduced by commit 9d71b54b65b1 ("dpll: netlink: Add
DPLL framework base functions") in 6.7-rc1.

Fixed status
Not fixed yet.

CVE-2023-6356: NULL pointer dereference in nvmet_tcp_build_iovec

CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

According to the Redhat Bugzilla, it describes that "There's a flaw in
Linux kernel's NVMe driver where an attacker can send crafted TCP
packets leading to NULL point dereference in nvmet_tcp_build_iovec. A
successfully attack can result in a remote Denial-of-service."

Fixed status
Not fixed yet.

CVE-2023-6535: NULL pointer dereference in nvmet_tcp_execute_request

CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

According to the Redhat Bugzilla, it describes that "There's a flaw in
Linux kernel's NVMe driver where an attacker can send crafted TCP
packets leading to NULL point dereference in nvmet_tcp_build_iovec. A
successfully attack can result in a remote Denial-of-service."

Fixed status
Not fixed yet.

CVE-2023-6536: NULL pointer dereference in __nvmet_req_complete

CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

According to the Redhat Bugzilla, it describes that "There's a flaw in
Linux kernel's NVMe driver where an attacker can send crafted
NVMe-oF/TCP packets leading to NULL point dereference in
__nvmet_req_complete. A successfuly attack can result in a remote
Denial-of-service."

Fixed status
Not fixed yet.

* Updated CVEs

CVE-2023-25775: improper access control flaw in RDMA driver

stable 4.14, 4.19, 5.10, and 5.4 were fixed.

Fixed status:
mainline: [bb6d73d9add68ad270888db327514384dfa44958]
stable/4.14: [92f871191e0bcb35dff37815579f15cac329955c]
stable/4.19: [f3c2760510c119c609e751c5a0b06cec6ae4bb4d]
stable/5.10: [ac65f8979b0eaac80c4710729c509d8837d8fdb7]
stable/5.4: [518b7f7d87aa87cf5173a937baa9a93fc6ed3d6d]
stable/6.1: [f01cfec8d3456bf389918eb898eda11f46d8b1b7]
stable/6.4: [ceba966f1d6391800cab3c1c9ac1661b5166bc5b]
stable/6.5: [782c5702b933477b088e80e6d07b9493145b2916]

CVE-2023-45898: ext4: fix slab-use-after-free in ext4_es_insert_extent()

stable 5.10 and 5.4 were fixed.

Fixed status
mainline: [768d612f79822d30a1e7d132a4d4b05337ce42ec]
stable/5.10: [10341e77e49fab3e095ae548ceb39335741b8fe9]
stable/5.15: [e33eb4997585f2e17513e3f2923080dc08cbb00b]
stable/5.4: [70edeedd795a634fdd99e757c7931b9e81686560]
stable/6.1: [8384d8c5cc398cf59ab829d71d750752002f0a21]
stable/6.5: [c15bf3330a9e3c01b23e59899a6a02432a62ddc3]

CVE-2023-6121: nvmet: nul-terminate the NQNs passed in the connect command

stable 5.10 and 5.4 were fixed.

Fixed status
mainline: [1c22e0295a5eb571c27b53c7371f95699ef705ff]
stable/5.10: [2be451e7a2f124899546c1bb5c6d509a927968c8]
stable/5.15: [e26c6febac43a2dd2c5fb993b2137489005d43bf]
stable/5.4: [afbedd6136cbff0b4412efd09d98d2cb7348563c]
stable/6.1: [0e485f12ebb7b69b67c7f85195a1b4aad95d354a]
stable/6.6: [2291653c27236d34ca7df3bfd3427ce6e30c2d95]

Currently tracking CVEs

CVE-2021-31615: Unencrypted Bluetooth Low Energy baseband links in
Bluetooth Core Specifications 4.0 through 5.2

There is no fix information.

CVE-2020-26556: kernel: malleable commitment Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26557: kernel: predictable Authvalue in Bluetooth Mesh
Provisioning Leads to MITM

No fix information.

CVE-2020-26559: kernel: Authvalue leak in Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26560: kernel: impersonation attack in Bluetooth Mesh Provisioning

No fix information.

Regards,
-- 
Masami Ichikawa
Cybertrust Japan Co., Ltd.

Email :masami.ichikawa@cybertrust.co.jp
          :masami.ichikawa@miraclelinux.com


^ permalink raw reply	[flat|nested] 33+ messages in thread

* [kernel-cve-report] New CVE entries this week
@ 2023-12-06 23:22 Masami Ichikawa
  0 siblings, 0 replies; 33+ messages in thread
From: Masami Ichikawa @ 2023-12-06 23:22 UTC (permalink / raw)
  To: cip-dev

Hi!

It's this week's CVE report.

This week reported 2 new CVEs and 2 updated CVEs.

A cpu vulnerability called "Spectre based on Linear Address Masking"
(shortly SLAM) was published this week.
For more information is in https://seclists.org/oss-sec/2023/q4/260.

* New CVEs

CVE-2023-24023: A man-in-the-middle attacks was found in Bluetooth
Core Specification 4.2 through 5.4

CVSS v3(NIST): 6.8 (MEDIUM)
CVSS v3(CNA): N/A

Bluetooth BR/EDR devices with Secure Simple Pairing and Secure
Connections pairing in Bluetooth Core Specification 4.2 through 5.4
allow certain man-in-the-middle attacks that force a short key length,
and might lead to discovery of the encryption key and live injection,
aka BLUFFS.

This CVE's CPE is assigned to bluetooth(vendor) and
bluetooth_core_specification(product).

Fixed status
Not yet.

CVE-2023-33053: Memory corruption in Kernel while parsing metadata.

CVSS v3(NIST): N/A
CVSS v3(CNA): 8.4 (HIGH)

Bug is in the qcom_mdt_read_metadata() in the
drivers/soc/qcom/mdt_loader.c. This function was introduced by commit
498b98e ("soc: qcom: mdt_loader: Support loading non-split images") in
5.3-rc1.
The qcom_mdt_read_metadata() doesn't check if ehdr->e_phnum is bigger
than PN_XNUM so if ehdr->e_phnum is bigger than PN_XNUM it will occur
an oob access.
According to the cip-kernel-config repo, no CIP member enables
CONFIG_QCOM_MDT_LOADER.

Fixed status
Patch is available(https://git.codelinaro.org/clo/la/kernel/msm-5.4/-/commit/06426824a281c9aef5bf0c50927eae9c7431db1e)
but it hasn't been merged into the mainline yet.

* Updated CVEs

CVE-2023-45898: ext4: fix slab-use-after-free in ext4_es_insert_extent()

stable 5.15 and 6.1 were fixed.

Fixed status:
mainline: [768d612f79822d30a1e7d132a4d4b05337ce42ec]
stable/5.15: [e33eb4997585f2e17513e3f2923080dc08cbb00b]
stable/6.1: [8384d8c5cc398cf59ab829d71d750752002f0a21]
stable/6.5: [c15bf3330a9e3c01b23e59899a6a02432a62ddc3]

CVE-2023-6121: nvmet: nul-terminate the NQNs passed in the connect command

stable 5.15, 6.1, and 6.6 were fixed.

Fixed status
mainline: [1c22e0295a5eb571c27b53c7371f95699ef705ff]
stable/5.15: [e26c6febac43a2dd2c5fb993b2137489005d43bf]
stable/6.1: [0e485f12ebb7b69b67c7f85195a1b4aad95d354a]
stable/6.6: [2291653c27236d34ca7df3bfd3427ce6e30c2d95]

Currently tracking CVEs

CVE-2021-31615: Unencrypted Bluetooth Low Energy baseband links in
Bluetooth Core Specifications 4.0 through 5.2

There is no fix information.

CVE-2020-26556: kernel: malleable commitment Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26557: kernel: predictable Authvalue in Bluetooth Mesh
Provisioning Leads to MITM

No fix information.

CVE-2020-26559: kernel: Authvalue leak in Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26560: kernel: impersonation attack in Bluetooth Mesh Provisioning

No fix information.

Regards,
-- 
Masami Ichikawa
Cybertrust Japan Co., Ltd.

Email :masami.ichikawa@cybertrust.co.jp
          :masami.ichikawa@miraclelinux.com


^ permalink raw reply	[flat|nested] 33+ messages in thread

* [kernel-cve-report] New CVE entries this week
@ 2023-11-29 23:03 Masami Ichikawa
  0 siblings, 0 replies; 33+ messages in thread
From: Masami Ichikawa @ 2023-11-29 23:03 UTC (permalink / raw)
  To: cip-dev

Hi!

It's this week's CVE report.

This week reported 1 new CVEs and 6 updated CVEs.

* New CVEs

CVE-2023-5972: Null pointer dereference bug was found in the netfilter

CVSS v3(NIST): N/A
CVSS v3(CNA): 7.0 (HIGH)

A null pointer dereference flaw was found in the nft_inner.c
functionality of netfilter in the Linux kernel.
This issue could allow a local user to crash the system or escalate
their privileges on the system.

This bug was introduced by commit 3a07327 ("netfilter: nft_inner:
support for inner tunnel header matching") in 6.2-rc1.
This bug is not affected prior to 6.2.

Fixed status
mainline: [505ce0630ad5d31185695f8a29dde8d29f28faa7,
52177bbf19e6e9398375a148d2e13ed492b40b80]
stable/6.5: [8a544721329e711f85358f73fe56964cdedeb531,
d6ba6de49c2d52df811513515ea17ecbbb6ba51a]

* Updated CVEs

CVE-2023-6121: nvmet: nul-terminate the NQNs passed in the connect command

Fixed in the mainline in 6.7-rc3.

Fixed status
mainline: [1c22e0295a5eb571c27b53c7371f95699ef705ff]

CVE-2023-0590: net: sched: fix race condition in qdisc_graft()

stable/4.19 and 4.14 were fixed.

Fixed status
mainline: [ebda44da44f6f309d302522b049f43d6f829f7aa]
stable/4.14: [42c50c7efcd1d263455438b81fe9388e685bfb66]
stable/4.19: [f782929b90b5ac88d4445c853949d9efa6db6bae]
stable/5.10: [7aa3d623c11b9ab60f86b7833666e5d55bac4be9]
stable/5.15: [ce1234573d183db1ebcab524668ca2d85543bf80]
stable/5.4: [0f5c0e0a4c0b081e5f959578a8e56c7921e63a2d]

CVE-2023-4244: A use-after-free vulnerability in the Linux kernel's netfilter

stable/5.4 was fixed.

Fixed status
mainline: [5f68718b34a531a556f2f50300ead2862278da26,
f6c383b8c31a93752a52697f8430a71dcbc46adf,
  c92db3030492b8ad1d0faace7a93bbcf53850d0c,
a2dd0233cbc4d8a0abb5f64487487ffc9265beb5,
  24138933b97b055d486e8064b4a1721702442a9b,
6a33d8b73dfac0a41f3877894b38082bd0c9a5bc,
  02c6c24402bf1c1e986899c14ba22a10b510916b,
23185c6aed1ffb8fc44087880ba2767aba493779]
stable/4.19: [255bb7fd670589c00cb2f8a1353b721306135ca3]
stable/5.10: [448be0774882f95a74fa5eb7519761152add601b,
146c76866795553dbc19998f36718d7986ad302b,
  77046cb00850e35ba935944b5100996b2ce34bba,
911dd3cdf1083f4c2e7df72aaab486a1d6dbcc0a,
  b15ea4017af82011dd55225ce77cce3d4dfc169c,
4046f2b56e5a7ba7e123ff961dd51187b8d59e78,
  dc0b1f019554e601f57e78d8f5c70e59d77e49a5,
a7653eaea0a59a6993c62d3653af5c880ce28533]
stable/5.4: [bbdb3b65aa91aa0a32b212f27780b28987f2d94f,
c357648929c8dff891502349769aafb8f0452bc2,
  85520a1f1d879455a8b6c950e7a92d3e8fa667b6,
1398a0eee290e3ddf1d5ce2539e47dd41830a0d5,
  1da4874d05da1526b11b82fc7f3c7ac38749ddf8,
29ff9b8efb84070b2ee9cf238efe0b202df079ff,
  b76dcf4662235b6f1a942892230a880382a3471d,
81da9e2c42556ada249cfb0d1d65d65986ac31ca]
stable/6.1: [7148bca63b212fc8e5c2e8374e14cd62b1c8441c,
59dab3bf0b8fc08eb802721c0532f13dd89209b8,
  ea3eb9f2192e4fc33b795673e56c97a21987f868,
df650d6a4bf47248261b61ef6b174d7c54034d15,
  4ead4f74b3a9162b205f702d72d4a3421356dbc1,
0b9af4860a61f55cf716267b5ae5df34aacc4b39,
  41113aa5698ad7a82635bcb747d483e4458d518d,
afa584c35065051a11ae3ea3cc105b634053fcd8]

CVE-2023-4563: Use-after-free in nft_verdict_dump due to a race
between set GC and transaction

stable/5.4 was fixed.

Fixed status
mainline: [24138933b97b055d486e8064b4a1721702442a9b,
5f68718b34a531a556f2f50300ead2862278da26,
  f6c383b8c31a93752a52697f8430a71dcbc46adf,
c92db3030492b8ad1d0faace7a93bbcf53850d0c,
  a2dd0233cbc4d8a0abb5f64487487ffc9265beb5,
6a33d8b73dfac0a41f3877894b38082bd0c9a5bc,
  02c6c24402bf1c1e986899c14ba22a10b510916b,
23185c6aed1ffb8fc44087880ba2767aba493779]
stable/5.10: [b15ea4017af82011dd55225ce77cce3d4dfc169c,
448be0774882f95a74fa5eb7519761152add601b,
  146c76866795553dbc19998f36718d7986ad302b,
77046cb00850e35ba935944b5100996b2ce34bba,
  911dd3cdf1083f4c2e7df72aaab486a1d6dbcc0a,
4046f2b56e5a7ba7e123ff961dd51187b8d59e78,
  dc0b1f019554e601f57e78d8f5c70e59d77e49a5,
a7653eaea0a59a6993c62d3653af5c880ce28533]
stable/5.4: [1da4874d05da1526b11b82fc7f3c7ac38749ddf8,
bbdb3b65aa91aa0a32b212f27780b28987f2d94f,
  c357648929c8dff891502349769aafb8f0452bc2,
85520a1f1d879455a8b6c950e7a92d3e8fa667b6,
  1398a0eee290e3ddf1d5ce2539e47dd41830a0d5,
29ff9b8efb84070b2ee9cf238efe0b202df079ff,
  b76dcf4662235b6f1a942892230a880382a3471d,
81da9e2c42556ada249cfb0d1d65d65986ac31ca]

CVE-2023-46862: io_uring/fdinfo: lock SQ thread while retrieving thread cpu/pid

stable/5.10 and 5.15 were fixed.

Fixed status
mainline: [7644b1a1c9a7ae8ab99175989bfc8676055edb46]
stable/5.10: [c6e8af2a8a63e0957284c16003c501e4a058e8d9]
stable/5.15: [3d7912710e5e187217313fea5c145881cfeaf952]
stable/6.1: [9236d2ea6465b37c0a73d994c1ad31753d31e5f5]
stable/6.5: [56e08ccc969796168f0e6adf6642f8546f54ba6f]

CVE-2023-6111: netfilter: nf_tables: remove catchall element in GC sync path

stable/5.15, 6.1, 6.5, and 6.6 were fixed.

Fixed status
mainline: [93995bf4af2c5a99e2a87f0cd5ce547d31eb7630]
stable/5.15: [0d9506c766c9601fe22d15584a99c704d7941ef6]
stable/6.1: [13e2d49647a7f137ebc063a4a9702dda80371b2e]
stable/6.5: [e3e68e617bfa8dfc8625d5e728b0fe4b4fb83876]
stable/6.6: [80d6a9236ab6d2c0fd241514d1af2e325d16a210]

Currently tracking CVEs

CVE-2021-31615: Unencrypted Bluetooth Low Energy baseband links in
Bluetooth Core Specifications 4.0 through 5.2

There is no fix information.

CVE-2020-26556: kernel: malleable commitment Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26557: kernel: predictable Authvalue in Bluetooth Mesh
Provisioning Leads to MITM

No fix information.

CVE-2020-26559: kernel: Authvalue leak in Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26560: kernel: impersonation attack in Bluetooth Mesh Provisioning

No fix information.

Regards,
-- 
Masami Ichikawa
Cybertrust Japan Co., Ltd.

Email :masami.ichikawa@cybertrust.co.jp
          :masami.ichikawa@miraclelinux.com


^ permalink raw reply	[flat|nested] 33+ messages in thread

* [kernel-cve-report] New CVE entries this week
@ 2023-11-22 23:21 Masami Ichikawa
  0 siblings, 0 replies; 33+ messages in thread
From: Masami Ichikawa @ 2023-11-22 23:21 UTC (permalink / raw)
  To: cip-dev

Hi!

It's this week's CVE report.

This week reported 3 new CVEs and 0 updated CVEs.

* New CVEs

CVE-2023-6121: nvmet: nul-terminate the NQNs passed in the connect command

CVSS v3(NIST): N/A
CVSS v3(CNA): 4.3 (MEDIUM)

An out-of-bounds read vulnerability was found in the NVMe-oF/TCP
subsystem in the Linux kernel. This flaw allows a remote attacker to
send a crafted TCP packet, triggering a heap-based buffer overflow
that results in kmalloc data to be printed (and potentially leaked) to
the kernel ring buffer (dmesg).

Fixed status
Patch is available at the linux-nvme list but it hasn't been merged yet.

CVE-2023-6176: A NULL pointer dereference bug was found in the net/tls/tls_sw.c

CVSS v3(NIST): N/A
CVSS v3(CNA): 4.4 (MEDIUM)

A null pointer dereference flaw was found in the Linux kernel API for
the cryptographic algorithm scatterwalk functionality. This issue
occurs when a user constructs a malicious packet with specific socket
configuration, which could allow a local user to crash the system or
escalate their privileges on the system.

This bug was introduced by commit 635d939 ("net/tls: free record only
on encryption error") in 5.7-rc7.
The commit 635d939 was backported to 5.4. So 5.4 or greater kernels
are affected by this issue.

Fixed status
mainline: [cfaa80c91f6f99b9342b6557f0f0e1143e434066]
stable/5.10: [a5096cc6e7836711541b7cd2d6da48d36fe420e9]
stable/5.15: [481bd6dcc5fe6c0ec57b61240ab552f67ff51b6b]
stable/5.4: [f9f3ce7719ebb437a883ae0db26723f17190df83]
stable/6.1: [7f4116c6f98412a6e29ace6d6a7b41ebb4e8a392]
stable/6.5: [74aecad5da19004ccf6321fd397d14b10756622a]

CVE-2023-6238: nvme: memory corruption via unprivileged user passthrough

CVSS v3(NIST): N/A
CVSS v3(CNA): 7.0 (HIGH)

A buffer overflow vulnerability was found in the NVM Express (NVMe)
driver in the Linux kernel. An unprivileged user could specify a small
meta buffer and let the device perform larger Direct Memory Access
(DMA) into the same buffer, overwriting unrelated kernel memory,
causing random kernel crashes and memory corruption.

Fixed status
Patch is available but it hasn't been merged yet.

* Updated CVEs

No updates


Currently tracking CVEs

CVE-2021-31615: Unencrypted Bluetooth Low Energy baseband links in
Bluetooth Core Specifications 4.0 through 5.2

There is no fix information.

CVE-2020-26556: kernel: malleable commitment Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26557: kernel: predictable Authvalue in Bluetooth Mesh
Provisioning Leads to MITM

No fix information.

CVE-2020-26559: kernel: Authvalue leak in Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26560: kernel: impersonation attack in Bluetooth Mesh Provisioning

No fix information.

Regards,
-- 
Masami Ichikawa
Cybertrust Japan Co., Ltd.

Email :masami.ichikawa@cybertrust.co.jp
          :masami.ichikawa@miraclelinux.com


^ permalink raw reply	[flat|nested] 33+ messages in thread

* [kernel-cve-report] New CVE entries this week
@ 2023-11-15 22:48 Masami Ichikawa
  0 siblings, 0 replies; 33+ messages in thread
From: Masami Ichikawa @ 2023-11-15 22:48 UTC (permalink / raw)
  To: cip-dev

Hi!

It's this week's CVE report.

This week reported 4 new CVEs and 0 updated CVEs.

* New CVEs

CVE-2023-39197: netfilter: conntrack: dccp: copy entire header to
stack buffer, not just basic one

CVSS v3(NIST): N/A

An out-of-bound access bug was found in the netfilter conntrack
feature. This vulnerability will expose sensitive information via DCCP
protocol to remote user.
This bug was introduced by commit 2bc7804 ("[NETFILTER]: nf_conntrack:
add DCCP protocol support") in 2.6.26-rc1.

Fixed status
mainline: [ff0a3a7d52ff7282dbd183e7fc29a1fe386b0c30]
stable/5.10: [9bdcda7abaf22f6453e5b5efb7eb4e524095d5d8]
stable/5.15: [c052797ac36813419ad3bfa54cb8615db4b41f15]
stable/5.4: [337fdce450637ea663bc816edc2ba81e5cdad02e]
stable/6.1: [26bd1f210d3783a691052c51d76bb8a8bbd24c67]

CVE-2023-39198: drm/qxl: fix UAF on handle creation

CVSS v3(NIST): N/A
CVSS v3(CNA): 7.5 (HIGH)

A race condition was found in the QXL driver in the Linux kernel. The
qxl_mode_dumb_create() function dereferences the qobj returned by the
qxl_gem_object_create_with_handle(), but the handle is the only one
holding a reference to it. This flaw allows an attacker to guess the
returned handle value and trigger a use-after-free issue, potentially
leading to a denial of service or privilege escalation.

Fixed status
mainline: [c611589b4259ed63b9b77be6872b1ce07ec0ac16]
stable/5.15: [d578c919deb786b4d6ba8c7639255cb658731671]
stable/6.1: [a1fa8f0fc58e0ec972f718030710efc442d7304b]

CVE-2023-6039: net: usb: lan78xx: reorder cleanup operations to avoid UAF bugs

CVSS v3(NIST): N/A
CVSS v3(CNA): 5.5 (MEDIUM)

A use-after-free flaw was found in lan78xx_disconnect in
drivers/net/usb/lan78xx.c in the network sub-component,
net/usb/lan78xx in the Linux Kernel. This flaw allows a local attacker
to crash the system when the LAN78XX USB device detaches.

Introduced by commit 77dfff5 ("lan78xx: Fix race condition in
disconnect handling") in 5.15-rc1. Prior to 5.15 kernels are not
affected.

Fixed status
mainline: [1e7417c188d0a83fb385ba2dbe35fd2563f2b6f3]

CVE-2023-6111: netfilter: nf_tables: remove catchall element in GC sync path

CVSS v3(NIST): N/A
CVSS v3(CNA): 7.8 (HIGH)

This bug was introduced by commit 4a9e12e ("netfilter: nft_set_pipapo:
call nft_trans_gc_queue_sync() in catchall GC") in 6.6-rc3.
This commit was backported to 5.15, 6.1, and 6.5 so that prior to 5.15
are not affected.

Fixed status
mainline: [93995bf4af2c5a99e2a87f0cd5ce547d31eb7630]

* Updated CVEs

No update.

Currently tracking CVEs

CVE-2021-31615: Unencrypted Bluetooth Low Energy baseband links in
Bluetooth Core Specifications 4.0 through 5.2

There is no fix information.

CVE-2020-26556: kernel: malleable commitment Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26557: kernel: predictable Authvalue in Bluetooth Mesh
Provisioning Leads to MITM

No fix information.

CVE-2020-26559: kernel: Authvalue leak in Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26560: kernel: impersonation attack in Bluetooth Mesh Provisioning

No fix information.

Regards,
-- 
Masami Ichikawa
Cybertrust Japan Co., Ltd.

Email :masami.ichikawa@cybertrust.co.jp
      :masami.ichikawa@miraclelinux.com


^ permalink raw reply	[flat|nested] 33+ messages in thread

* [kernel-cve-report] New CVE entries this week
@ 2023-11-08 22:55 Masami Ichikawa
  0 siblings, 0 replies; 33+ messages in thread
From: Masami Ichikawa @ 2023-11-08 22:55 UTC (permalink / raw)
  To: cip-dev

Hi!

It's this week's CVE report.

This week reported 1 new CVEs and 7 updated CVEs.

* New CVEs

CVE-2023-47233: Use after Free bug in brcmf_cfg80211_detach

CVSS v3(NIST): N/A

The brcm80211 component in the Linux kernel through 6.5.10 has a
brcmf_cfg80211_detach use-after-free in the device unplugging
(disconnect the USB by hotplug) code. For physically proximate
attackers with local access, this "could be exploited in a real world
scenario." This is related to brcmf_cfg80211_escan_timeout_worker in
drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c.

Introduced by commit e756af5 ("brcmfmac: add e-scan support.") in 3.7-rc1.

Fixed status
Not fixed yet

* Updated CVEs

CVE-2023-46862: io_uring/fdinfo: lock SQ thread while retrieving thread cpu/pid

Stable 6.1 and 6.5 were fixed.

Fixed status
mainline: [7644b1a1c9a7ae8ab99175989bfc8676055edb46]
stable/6.1: [9236d2ea6465b37c0a73d994c1ad31753d31e5f5]
stable/6.5: [56e08ccc969796168f0e6adf6642f8546f54ba6f]

CVE-2023-5158: vringh: don''t use vringh_kiov_advance() in vringh_iov_xfer()

Fixed in mainline, 5.15, 6.1, and 6.5.

Fixed status
mainline: [7aed44babc7f97e82b38e9a68515e699692cc100]
stable/5.15: [1e69422efcc60571cc04f6c1940da848a8c2f21b]
stable/6.1: [3a72decd6b49ff11a894aabd4d9b3025f046fe61]
stable/6.5: [0bf2b9c2f3545ffce5720de61c33fc171c0e480a]

CVE-2021-44879: f2fs: fix to do sanity check on inode type during
garbage collection

Stable 4.14, 4.19, 5.10, and 5.4 were fixed.

Fixed status
mainline: [9056d6489f5a41cfbb67f719d2c0ce61ead72d9f]
stable/4.14: [a481db81e7ead1369acca8e13b6939778cb7d2c5]
stable/4.19: [45c9da086dded78a12bc580f5bb012545a910803]
stable/5.10: [571ce7d944cdd204da163cb5d5cc75bb38090246]
stable/5.15: [0ddbdc0b7f0cec3815ac05a30b2c2f6457be3050]
stable/5.16: [d667b9f61df7bdfcb59dd1406fd2392c358f0008]
stable/5.4: [e9a988cd4c8baac7550aa0c2f1efc9533ed9da36]

CVE-2023-3567: use-after-free in vcs_read in drivers/tty/vt/vc_screen.c

Stable 4.14 was fixed.

Fixed status
mainline: [226fae124b2dac217ea5436060d623ff3385bc34]
stable/4.14: [af79ea9a2443016f64d8fd8d72020cc874f0e066]
stable/4.19: [6332f52f44b9776568bf3c0b714ddfb0bb175e78]
stable/5.10: [55515d7d8743b71b80bfe68e89eb9d92630626ab]
stable/5.15: [fc9e27f3ba083534b8bbf72ab0f5c810ffdc7d18]
stable/5.4: [d0332cbf53dad06a22189cc341391237f4ea6d9f]
stable/6.1: [8506f16aae9daf354e3732bcfd447e2a97f023df]

CVE-2023-45863: kobject: Fix slab-out-of-bounds in fill_kobj_path()

Stable 4.14, 4.19, 5.10, and 5.4 were fixed.

Fixed status
mainline: [3bb2a01caa813d3a1845d378bbe4169ef280d394]
stable/4.14: [b43cf5ad5241d6f33a02c93271a282d5ed6c4cce]
stable/4.19: [0af6c6c15681cf80aeb85fcb3a1928c63aa89deb]
stable/5.10: [b2e62728b106fe54f8618c21a252df7d4a4cc775]
stable/5.15: [89a0079049f5568268d75c8cdf28bec0e2553e23]
stable/5.4: [5776aeee2a604ccc03e8269713624f9c8fd318e0]
stable/6.1: [fe4dd80d58ec5633daf5d50671d1341f738508bf]

CVE-2023-5090: x86: KVM: SVM: always update the x2avic msr interception

Stable 6.1 was fixed.

Fixed status
mainline: [b65235f6e102354ccafda601eaa1c5bef5284d21]
stable/6.1: [7ab62e3415fb59289ab6dea31f0cc0237b949200]
stable/6.5: [94805f9d3a3fb1f091bcc08b9c4846c4346706eb]

CVE-2023-5178: nvmet-tcp: Fix a possible UAF in queue intialization setup

Stable 5.4 was fixed.

Fixed status
mainline: [d920abd1e7c4884f9ecd0749d1921b7ab19ddfbd]
stable/5.10: [e985d78bdcf37f7ef73666a43b0d2407715f00d3]
stable/5.15: [34f62612be2a7f90ab68a14154db6664a32f8db0]
stable/5.4: [4e53bab11f01a401a5acd3bc94335b27ec79106b]
stable/6.1: [f691ec5a548257edb3aacd952e2a574e4e57b2c4]
stable/6.5: [675f0e9bb716fa3252979145b9b1a950140e94e9]

Currently tracking CVEs

CVE-2021-31615: Unencrypted Bluetooth Low Energy baseband links in
Bluetooth Core Specifications 4.0 through 5.2

There is no fix information.

CVE-2020-26556: kernel: malleable commitment Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26557: kernel: predictable Authvalue in Bluetooth Mesh
Provisioning Leads to MITM

No fix information.

CVE-2020-26559: kernel: Authvalue leak in Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26560: kernel: impersonation attack in Bluetooth Mesh Provisioning

No fix information.

Regards,
-- 
Masami Ichikawa
Cybertrust Japan Co., Ltd.

Email :masami.ichikawa@cybertrust.co.jp
      :masami.ichikawa@miraclelinux.com


^ permalink raw reply	[flat|nested] 33+ messages in thread

* [kernel-cve-report] New CVE entries this week
@ 2023-11-01 22:42 Masami Ichikawa
  0 siblings, 0 replies; 33+ messages in thread
From: Masami Ichikawa @ 2023-11-01 22:42 UTC (permalink / raw)
  To: cip-dev

Hi!

It's this week's CVE report.

This week reported 2 new CVEs and 3 updated CVEs.

* New CVEs

CVE-2023-46813: SEV-ES local priv escalation for userspace that have
access to MMIO regions

CVSS v3(NIST): N/A

An issue was discovered in the Linux kernel before 6.5.9, exploitable
by local users with userspace access to MMIO registers. Incorrect
access checking in the #VC handler and instruction emulation of the
SEV-ES emulation of MMIO accesses could lead to arbitrary write access
to kernel memory (and thus privilege escalation). This depends on a
race condition through which userspace can replace an instruction
before the #VC handler reads it.

This feature has been introduced since 5.10 so before 5.10 kernels are
not affected.
It was fixed in 6.6-rc7.

Fixed status
mainline: [63e44bc52047f182601e7817da969a105aa1f721,
b9cb9c45583b911e0db71d09caa6b56469eb2bdf,
  a37cd2a59d0cb270b1bba568fd3a3b8668b9d3ba]
stable/5.10: [6550cbe25de182f6c0176909a90b324cb375133f,
5bb9ba7dafbe18e027e335f74372ca65f07f7edd,
  d78c5d8c23c3f0e24168ea98760016665bf92a79]
stable/6.1: [57d0639f60f1ff04cbe7fd52823b94b894d7f812,
def94eb9a804acdcdba5b959ad72cf9119f03f3b,
  95ff590b802757f8b6bd32e7e5b21ef9b91e2583]

CVE-2023-46862: io_uring/fdinfo: lock SQ thread while retrieving thread cpu/pid

CVSS v3(NIST): N/A

An issue was discovered in the Linux kernel through 6.5.9. During a
race with SQ thread exit, an io_uring/fdinfo.c io_uring_show_fdinfo
NULL pointer dereference can occur.

It looks like commit dbbe9c6 (" io_uring: show sqthread pid and cpu in
fdinfo") introduced this issue since 5.10-rc1.

Fixed status
mainline: [7644b1a1c9a7ae8ab99175989bfc8676055edb46]

* Updated CVEs

CVE-2023-1193: use-after-free in setup_async_work()

The mainline was fixed.

Fixed status
mainline: [3a9b557f44ea8f216aab515a7db20e23f0eb51b9]

CVE-2023-35827: net: ravb: Fix possible UAF bug in ravb_remove

The mainline, 5.10, 5.15, 5.4, 6.1, and 6.5 were fixed.

Fixed status
mainline: [3971442870713de527684398416970cf025b4f89]
stable/5.10: [db9aafa19547833240f58c2998aed7baf414dc82]
stable/5.15: [616761cf9df9af838c0a1a1232a69322a9eb67e6]
stable/5.4: [65d34cfd4e347054eb4193bc95d9da7eaa72dee5]
stable/6.1: [6f6fa8061f756aedb93af12a8a5d3cf659127965]
stable/6.5: [105abd68ad8f781985113aee2e92e0702b133705]

CVE-2023-4610: slab-use-after-free Read in radix_tree_lookup while
fuzzing Linux kernel 6.4-rc6 with syzkaller

The mainline was fixed. This fix reverts commit f95bdb7 ("mm: vmscan:
make global slab shrink lockless") that was merged in 6.4-rc1.

Fixed status
mainline: [71c3ad65fabec9620d3f548b2da948c79c7ad9d5]

CVE-2023-5158: vringh: don''t use vringh_kiov_advance() in vringh_iov_xfer()

Fixed in mainline, 5.15, 6.1, and 6.5.

Fixed status
mainline: [7aed44babc7f97e82b38e9a68515e699692cc100]
stable/5.15: [1e69422efcc60571cc04f6c1940da848a8c2f21b]
stable/6.1: [3a72decd6b49ff11a894aabd4d9b3025f046fe61]
stable/6.5: [0bf2b9c2f3545ffce5720de61c33fc171c0e480a]

Currently tracking CVEs

CVE-2021-31615: Unencrypted Bluetooth Low Energy baseband links in
Bluetooth Core Specifications 4.0 through 5.2

There is no fix information.

CVE-2020-26556: kernel: malleable commitment Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26557: kernel: predictable Authvalue in Bluetooth Mesh
Provisioning Leads to MITM

No fix information.

CVE-2020-26559: kernel: Authvalue leak in Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26560: kernel: impersonation attack in Bluetooth Mesh Provisioning

No fix information.

Regards,
-- 
Masami Ichikawa
Cybertrust Japan Co., Ltd.

Email :masami.ichikawa@cybertrust.co.jp
      :masami.ichikawa@miraclelinux.com


^ permalink raw reply	[flat|nested] 33+ messages in thread

* [kernel-cve-report] New CVE entries this week
@ 2023-10-25 23:30 Masami Ichikawa
  0 siblings, 0 replies; 33+ messages in thread
From: Masami Ichikawa @ 2023-10-25 23:30 UTC (permalink / raw)
  To: cip-dev

Hi!

It's this week's CVE report.

This week reported 3 new CVEs and 1 updated CVEs.

* New CVEs

CVE-2023-5090: x86: KVM: SVM: always update the x2avic msr interception

CVSS v3(NIST): N/A

The svm_set_x2apic_msr_interception() is used to call intercept x2apic mars.
However, the svm_set_x2apic_msr_interception() has incorrect check for
 "'!apic_x2apic_mode()" which prevent it from doing anything in this
case. As a result of this, all x2apic msrs are left unintercepted, and
that exposes the bare metal x2apic (if enabled) to the guest.

Introduced by commit 4d1d794 ("KVM: SVM: Introduce logic to
(de)activate x2AVIC mode") in 6.0-rc1.
Before 6.0 LTS kernels don't contain the commit.

Fixed status
mainline: [b65235f6e102354ccafda601eaa1c5bef5284d21]
stable/6.5: [94805f9d3a3fb1f091bcc08b9c4846c4346706eb]

CVE-2023-5717: perf: Disallow mis-matched inherited group reads

CVSS v3(NIST): N/A
CVSS v3(CNA): 7.8 HIGH

A heap out-of-bounds write vulnerability in the Linux kernel's Linux
Kernel Performance Events (perf) component can be exploited to achieve
local privilege escalation. If perf_read_group() is called while an
event's sibling_list is smaller than its child's sibling_list, it can
increment or write to memory locations outside of the allocated
buffer.

This bug was introduced by commit fa8c269 ("perf/core: Invert
perf_read_group() loops") in 4.4-rc1. Fixed in 6.6-rc7.

Fixed status
mainline: [32671e3799ca2e4590773fd0e63aaa4229e50c06]
stable/4.14: [555e15e93f6dbb8ce6b5b92e5272473abfe8bd2b]
stable/4.19: [a714491fa92d2068358dd603cc50bf2062517bd8]
stable/5.10: [487a8e24643a0effb2ba19cad3227fc75dc3c4b7]
stable/5.15: [71d224acc4d1df1b61a294abee0f1032a9b03b40]
stable/5.4: [7252c8b981853bb8930de44fab924f947362683f]
stable/6.1: [f6952655a61264900ed08e9d642adad8222f8e29]
stable/6.5: [20f925d38e1ecc1d36ee6bf6e325fb514a6f727d]

CVE-2023-5633: drm/vmwgfx: Keep a gem reference to user bos in surfaces

The reference count changes made as part of the CVE-2023-33951 and
CVE-2023-33952 fixes exposed a use-after-free flaw in the way memory
objects were handled when they were being used to store a surface.
When running inside a VMware guest with 3D acceleration enabled, a
local, unprivileged user could potentially use this flaw to escalate
their privileges.

CVSS v3(NIST): N/A
CVSS v3(CNA): 7.8(HIGH)

This bug was introduced by commit a950b98 ("drm/vmwgfx: Do not drop
the reference to the handle too soon") in 6.2.
This commit is not backported to 5.x and 4.x kernels. It is fixed in 6.6-rc6.

Fixed status
mainline: [91398b413d03660fd5828f7b4abc64e884b98069]
stable/6.5: [1474b39f961703d0bb33833a6d6b112826839781]

* Updated CVEs

CVE-2023-5178: nvmet-tcp: Fix a possible UAF in queue intialization setup

The mainline was fixed in 6.6-rc7.
This bug was introduced by commit 872d26a ("nvmet-tcp: add NVMe over
TCP target driver") in 5.0-rc1. Linux 4.x kernels are not affected.

Fixed status
mainline: [d920abd1e7c4884f9ecd0749d1921b7ab19ddfbd]
stable/5.10: [e985d78bdcf37f7ef73666a43b0d2407715f00d3]
stable/5.15: [34f62612be2a7f90ab68a14154db6664a32f8db0]
stable/6.1: [f691ec5a548257edb3aacd952e2a574e4e57b2c4]
stable/6.5: [675f0e9bb716fa3252979145b9b1a950140e94e9]

Currently tracking CVEs

CVE-2021-31615: Unencrypted Bluetooth Low Energy baseband links in
Bluetooth Core Specifications 4.0 through 5.2

There is no fix information.

CVE-2020-26556: kernel: malleable commitment Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26557: kernel: predictable Authvalue in Bluetooth Mesh
Provisioning Leads to MITM

No fix information.

CVE-2020-26559: kernel: Authvalue leak in Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26560: kernel: impersonation attack in Bluetooth Mesh Provisioning

No fix information.

Regards,
-- 
Masami Ichikawa
Cybertrust Japan Co., Ltd.

Email :masami.ichikawa@cybertrust.co.jp
      :masami.ichikawa@miraclelinux.com


^ permalink raw reply	[flat|nested] 33+ messages in thread

* [kernel-cve-report] New CVE entries this week
@ 2023-10-18 23:20 Masami Ichikawa
  0 siblings, 0 replies; 33+ messages in thread
From: Masami Ichikawa @ 2023-10-18 23:20 UTC (permalink / raw)
  To: cip-dev

Hi !

It's this week's CVE report.

This week reported 6 new CVEs and 1 updated CVE.

* New CVEs

CVE-2023-5178: nvmet-tcp: Fix a possible UAF in queue intialization setup

CVSS v3 score is not provided.

A logical bug in the NVMe-oF/TCP subsystem. A malicious actor, with
the ability to send messages to the NVMe-oF/TCP server (either LAN or
WAN), can cause a use-after-free and a double free, which may lead to
remote kernel code execution.

Fixed status
Patch is available
(https://lore.kernel.org/all/20231004173226.5992-1-sj@kernel.org/T/)
but it has not merged into the mainline yet as of 2023-10-16.

CVE-2023-40791: crypto, cifs: fix error handling in extract_iter_to_sg()

CVSS v3 score is not provided.

extract_user_to_sg in lib/scatterlist.c in the Linux kernel before
6.4.12 fails to unpin pages in a certain situation, as demonstrated by
a WARNING for try_grab_page.

Introduced by commit 0185846 ("netfs: Add a function to extract an
iterator into a scatterlist") in 6.3-rc1. Fixed in 6.5-rc6.
LTS kernels are not affected.

Fixed status
mainline: [f443fd5af5dbd531f880d3645d5dd36976cf087f]

CVE-2023-45862: USB: ene_usb6250: Allocate enough memory for full object

CVSS v3 score is not provided.

An issue was discovered in drivers/usb/storage/ene_ub6250.c for the
ENE UB6250 reader driver in the Linux kernel before 6.2.5. An object
could potentially extend beyond the end of an allocation.

Fixed status
mainline: [ce33e64c1788912976b61314b56935abd4bc97ef]
stable/4.14: [26f31c6e1389c23a1b822a61c59d5d1f357cb478]
stable/4.19: [cef5e33d8b893891817236db819982f87943e8fd]
stable/5.10: [961f93d63da72f5fcaa6793fb2dcbc995c119a8e]
stable/5.15: [7e902b949600c51c94d06b137f874126a27e6557]
stable/5.4: [da4e715a466ca982d4584da21ea385f28ca79ce6]
stable/6.1: [ff542083b105c9c72d83899d3f74eeec354f808e]

CVE-2023-45863: kobject: Fix slab-out-of-bounds in fill_kobj_path()

CVSS v3 score is not provided.

An issue was discovered in lib/kobject.c in the Linux kernel before
6.2.3. With root access, an attacker can trigger a race condition that
results in a fill_kobj_path out-of-bounds write.

All LTS kernels are affected. It is fixed in 6.3-rc1.

Fixed status
mainline: [3bb2a01caa813d3a1845d378bbe4169ef280d394]
stable/5.15: [89a0079049f5568268d75c8cdf28bec0e2553e23]
stable/6.1: [fe4dd80d58ec5633daf5d50671d1341f738508bf]

CVE-2023-45871: igb: set max size RX buffer when store bad packet is enabled

CVSS v3 score is not provided.

An issue was discovered in drivers/net/ethernet/intel/igb/igb_main.c
in the IGB driver in the Linux kernel before 6.5.3. A buffer size may
not be adequate for frames larger than the MTU.

It was introduced by commit 89eaefb ("igb: Support RX-ALL
featureflag.") in 3.4-rc1. Fixed in 6.6-rc1.

Fixed status
mainline: [bb5ed01cd2428cd25b1c88a3a9cba87055eb289f]
stable/4.14: [017d5c8eef06178e4148db273df03b7ad9eeb5bc]
stable/4.19: [981d0bc43e8d5482294432677e80a1d15f4b790d]
stable/5.10: [3e39008e9e3043663324f0920a5d6ebfa68cc92a]
stable/5.15: [be7353af5b35c8f4a11573a38b997f74f8c2ae4b]
stable/5.4: [c2ad60ed38b872aa971408b8b8eaad7a91501b37]
stable/6.1: [d2e906c725979c39ebf120a189e521ceae787d26]
stable/6.5: [dad92377fc6e012e481c6f4a75e32e48fe2777db]

CVE-2023-45898: ext4: fix slab-use-after-free in ext4_es_insert_extent()

CVSS v3 score is not provided.

The Linux kernel before 6.5.4 has an es1 use-after-free in
fs/ext4/extents_status.c, related to ext4_es_insert_extent.

Introduced by commit 2a69c45 ("ext4: using nofail preallocation in
ext4_es_insert_extent()") in 6.5-rc1. Fixed in 6.6-rc1.
LTS kernels are not affected.

Fixed status
mainline: [768d612f79822d30a1e7d132a4d4b05337ce42ec]
stable/6.5: [c15bf3330a9e3c01b23e59899a6a02432a62ddc3]

* Updated CVEs

CVE-2023-31085: BUG: divide error in ubi_attach_mtd_dev

Fixed in the mainline and all stable kernels.
It was introduced by commit 801c135 ("UBI: Unsorted Block Images") in
2.6.22-rc1. Fixed in 6.6-rc5.

Fixed status
mainline: [017c73a34a661a861712f7cc1393a123e5b2208c]
stable/4.14: [ef7a4c97a85ab1bff7abc98f885678bd33bb4881]
stable/4.19: [a0d71e9e61da8a85a46774c67549739e28fda795]
stable/5.10: [a5f643ab11631095c60c9852705220edf1659d6f]
stable/5.15: [0ea2a63497333019bd2931975ed489216b365755]
stable/5.4: [c6d358387632a6d45b3e5d4c310cfec1bde59423]
stable/6.1: [91aeb418b9175d09fc858f0fdf01988cbf990c5d]
stable/6.5: [87b9858e404069817cd4b31830e0a1b9b3d183c4]

Currently tracking CVEs

CVE-2021-31615: Unencrypted Bluetooth Low Energy baseband links in
Bluetooth Core Specifications 4.0 through 5.2

There is no fix information.

CVE-2020-26556: kernel: malleable commitment Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26557: kernel: predictable Authvalue in Bluetooth Mesh
Provisioning Leads to MITM

No fix information.

CVE-2020-26559: kernel: Authvalue leak in Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26560: kernel: impersonation attack in Bluetooth Mesh Provisioning

No fix information.

Regards,
-- 
Masami Ichikawa
Cybertrust Japan Co., Ltd.

Email :masami.ichikawa@cybertrust.co.jp
      :masami.ichikawa@miraclelinux.com


^ permalink raw reply	[flat|nested] 33+ messages in thread

* [kernel-cve-report] New CVE entries this week
@ 2023-10-11 22:54 Masami Ichikawa
  0 siblings, 0 replies; 33+ messages in thread
From: Masami Ichikawa @ 2023-10-11 22:54 UTC (permalink / raw)
  To: cip-dev

Hi !

It's this week's CVE report.

This week reported 6 new CVEs and 8 updated CVEs.

* New CVEs

CVE-2023-39191: eBPF: insufficient stack type checks in dynptr

CVSS v3 score is not provided (NIST).
CVSS v3 score is 8.2 HIGH (CNA).

An improper input validation flaw was found in the eBPF subsystem in
the Linux kernel. The issue occurs due to a lack of proper validation
of dynamic pointers within user-supplied eBPF programs prior to
executing them. This may allow an attacker with CAP_BPF privileges to
escalate privileges and execute arbitrary code in the context of the
kernel.

It introduced by commit Fixes: 97e03f521050 ("bpf: Add verifier
support for dynptrs") in 5.19-rc1.
Fixed in 6.3-rc1 in the mainline.

Fixed status
mainline: [d6fefa1105dacc8a742cdcf2f4bfb501c9e61349,
79168a669d8125453c8a271115f1ffd4294e61f6,
  ef8fc7a07c0e161841779d6fe3f6acd5a05c547c,
f8064ab90d6644bc8338d2d7ff6a0d6e7a1b2ef3,
  379d4ba831cfa895d0cc61d88cd0e1402f35818c,
f5b625e5f8bbc6be8bb568a64d7906b091bc7cb0,
  1ee72bcbe48de6dcfa44d6eba0aec6e42d04cd4d,
91b875a5e43b3a8dec4fbdca067c8860004b5f0e,
  f4d24edf1b9249e43282ac2572d43d9ad10faf43,
ef4810135396735c1a6b1c343c3cc4fe4be96a43,
  011edc8e49b8551dfb6cfcc8601d05e029cf5994,
ae8e354c497af625eaecd3d86e04f9087762d42b]

CVE-2023-39192: netfilter: xt_u32: validate user space input

CVSS v3 score is 6.0 MEDIUM (NIST).
CVSS v3 score is 6.7 MEDIUM (CNA).

This vulnerability allows local attackers to disclose sensitive
information on affected installations of the Linux Kernel. An attacker
must first obtain the ability to execute high-privileged code on the
target system in order to exploit this vulnerability.

The specific flaw exists within the u32_match_it function. The issue
results from the lack of proper validation of user-supplied data,
which can result in a read past the end of an allocated data
structure. An attacker can leverage this in conjunction with other
vulnerabilities to execute arbitrary code in the context of the
kernel.

Introduced by commit 1b50b8a ("[NETFILTER]: Add u32 match") in 2.6.23-rc1.
Fixed in 6.6-rc1 in the mainline.

Fixed status
cip/4.4-st: [023311531a6ae3aa7e3d6ca27da52988cef78453]
mainline: [69c5d284f67089b4750d28ff6ac6f52ec224b330]
stable/4.14: [e416d65ff456066d60d813c540ab2dd2a06d3d12]
stable/4.19: [ddf190be80ef0677629416a128f9da91e5800d21]
stable/5.10: [a1b711c370f5269f4e81a07e7542e351c0c4682e]
stable/5.15: [b3d07714ad24e51ff6fc6dced3bd3d960e99ac25]
stable/5.4: [28ce8495b5599abaa4b4f0bbb45f1f8e89b07e15]
stable/6.1: [1c164c1e9e93b0a72a03a7edb754e3857d4e4302]
stable/6.5: [799cc0fb184408f688b030ea381844b16d1d9c62]

CVE-2023-39193: netfilter: xt_sctp: validate the flag_info count

CVSS v3 score is 6.0 MEDIUM (NIST).
CVSS v3 score is 5.1 MEDIUM (CNA).

Introduced by commit 2e4e6a1 ("[NETFILTER] x_tables: Abstraction layer
for {ip,ip6,arp}_tables") in 2.6.16-rc1.

This vulnerability allows local attackers to disclose sensitive
information on affected installations of the Linux Kernel. An attacker
must first obtain the ability to execute high-privileged code on the
target system in order to exploit this vulnerability.

The specific flaw exists within the match_flags function. The issue
results from the lack of proper validation of user-supplied data,
which can result in a read past the end of an allocated data
structure. An attacker can leverage this in conjunction with other
vulnerabilities to execute arbitrary code in the context of the
kernel.

Introduced by commit 2e4e6a1 ("[NETFILTER] x_tables: Abstraction layer
for {ip,ip6,arp}_tables") in 2.6.16-rc1.
Fixed in 6.6-rc1 in the mainline.

Fixed status
cip/4.4-st: [ad14bd8357a265ce12ebe9698db3c66ab8110bc5]
mainline: [e99476497687ef9e850748fe6d232264f30bc8f9]
stable/4.14: [be52e3c14651ade0f4539f319f9f0c40a230b076]
stable/4.19: [f25dbfadaf525d854597c16420dd753ca47b9396]
stable/5.10: [5541827d13cf19b905594eaee586527476efaa61]
stable/5.15: [267a29f8bfdb949ad2a03a3b6d7ad42aeb4c2bab]
stable/5.4: [64831fb6a2040c25473ff8c8e85b3a42bd38494c]
stable/6.1: [4921f9349b66da7c5a2b6418fe45e9ae0ae72924]
stable/6.5: [85ebbbe845823be6f8c04b4901da9a0a6f866283]

CVE-2023-39194: net: xfrm: Fix xfrm_address_filter OOB read

CVSS v3 score is 2.3 LOW (NIST).
CVSS v3 score is 3.2 LOW (CNA).

This vulnerability allows local attackers to disclose sensitive
information on affected installations of the Linux Kernel. An attacker
must first obtain the ability to execute high-privileged code on the
target system in order to exploit this vulnerability.

The specific flaw exists within the processing of state filters. The
issue results from the lack of proper validation of user-supplied
data, which can result in a read past the end of an allocated buffer.
An attacker can leverage this in conjunction with other vulnerabilties
to escalate privileges and execute arbitrary code in the context of
the kernel.

Introduced by commit d362309 ("ipsec: add support of limited SA dump")
in 3.15-rc1.
Fixed in 6.5-rc7 in the mainline.

Fixed status
cip/4.4: [f5973308eb3a388a3a1c02a67ebf60e2c9355ff8]
cip/4.4-st: [f5973308eb3a388a3a1c02a67ebf60e2c9355ff8]
mainline: [dfa73c17d55b921e1d4e154976de35317e43a93a]
stable/4.14: [0a42d1335985f9ebfbc997944ba8b1d84b9b661e]
stable/4.19: [a695f0e724330773283a6d67e149363b89087f76]
stable/5.10: [7e50815d29037e08d3d26f3ebc41bcec729847b7]
stable/5.15: [1960f468078b3471d1ee9aafa0cf06c8c34a505f]
stable/5.4: [373848d51fde9138cdc539b1d97dc6b301cc04d5]
stable/6.1: [9a0056276f5f38e188732bd7b6949edca6a80ea1]

CVE-2023-39189: netfilter: nfnetlink_osf: avoid OOB read

A flaw was found in the Netfilter subsystem in the Linux kernel. The
nfnl_osf_add_callback function did not validate the user mode
controlled opt_num field. This flaw allows a local privileged
(CAP_NET_ADMIN) attacker to trigger an out-of-bounds read, leading to
a crash or information disclosure.

Introduced by commit 11eeef4 ("netfilter: passive OS fingerprint
xtables match") in 2.6.31-rc1. Fixed in 6.6-rc1.

CVSS v3 score is 6.0 MEDIUM (NIST).
CVSS v3 score is 5.1 MEDIUM (CNA).

Fixed status
mainline: [f4f8a7803119005e87b716874bec07c751efafec]
stable/4.19: [40d427ffccf9e60bd7288ea3748c066404a35622]
stable/5.10: [780f60dde29692c42091602fee9c25e9e391f3dc]
stable/5.15: [19280e8dfb52cf9660760fdc86e606e0653170fa]
stable/5.4: [a44602888bbe89d9dd89cb84baed2e356aba7436]
stable/6.1: [7bb8d52b4271be7527b6e3120ae6ce4c6cdf6e34]
stable/6.5: [a3d0f898b80ac9b049e590b3ee6391716002da17]

CVE-2023-34324: xen/events: replace evtchn_rwlock with RCU

CVSS v3 score is not provided.

A (malicious) guest administrator could cause a denial of service (DoS)
in a backend domain (other than dom0) by disabling a paravirtualized
device.

A malicious backend could cause DoS in a guest running a Linux kernel by
disabling a paravirtualized device.

Introduced by commit 54c9de8 ("xen/events: add a new "late EOI" evtchn
framework") in 5.10-rc1.
This commit was backported to older kernels. cip/4.4-st, cip/4.4, and
cip/4.4-rt contain this commit that hash is
1d762cb6676b5f9c57c6ac56856e540529a8d928.

Fixed status
mainline: [87797fad6cce28ec9be3c13f031776ff4f104cfc]
stable/4.14: [bc32110d6176cc34c58f4efa22194546f103b81a]
stable/4.19: [3fdf2be9089b5096a28e76376656c60ce410ac4a]
stable/5.10: [660627c71bc1098aa94e5f208f14748b105b73bc]
stable/5.15: [c8af81a9d36e0d2e5f198eaceb38a743d834dfe2]
stable/5.4: [f70c285cf02c2430da74c58b8a177fcb5df6ca43]
stable/6.1: [a4cc925e2e12c3bbffb0860acdb9f9c1abde47dd]
stable/6.5: [76b33722e2d2336a6e2a7d9eacbbb8988478cf98]

* Updated CVEs

CVE-2023-42754: null pointer dereference in Linux kernel ipv4 stack

Stable 4.14, 4.19, 5.10, 5.15, 5.4, 6.1, and 6.5 were fixed.

Fixed status
mainline: [0113d9c9d1ccc07f5a3710dac4aa24b6d711278c]
stable/4.14: [084c7ac9e8d60bf21a423490021b7c3427312955]
stable/4.19: [a2cf7bd75b3992e8df68dd5fdc6499b67d45f6e0]
stable/5.10: [8689c9ace976d6c078e6dc844b09598796e84099]
stable/5.15: [8860d354f653628b6330e1c5b06b2828948135a4]
stable/5.4: [810fd23d9715474aa27997584e8fc9396ef3cb67]
stable/6.1: [2712545e535d7a2e4c53b9c9658a9c88c6055862]
stable/6.5: [cda20fcddf53f0f959641c8ef4d50ab87ffa5124]

CVE-2023-42756: netfilter: ipset: Fix race between IPSET_CMD_CREATE
and IPSET_CMD_SWAP

Stable 5.10, 5.15, 5.4, 6.1, and 6.5 were fixed.

Fixed status
mainline: [7433b6d2afd512d04398c73aa984d1e285be125b]
stable/5.10: [f1893feb20ea033bcd9c449b55df3dab3802c907]
stable/5.15: [a70dbdede0c7173d4a44247a454d1015e361b72d]
stable/5.4: [02a233986c9eaabfce0b08362189743e4809f579]
stable/6.1: [ea5a61d58886ae875f1b4a371999f2a8b58cf26d]
stable/6.5: [20a93d402b6fe6757e14b0eeb400dfac8b8aa3ad]

CVE-2023-5197: netfilter: nf_tables: disallow rule removal from chain binding

Stable 5.10, 5.15 and 6.5 were fixed.

Fixed status
mainline: [f15f29fd4779be8a418b66e9d52979bb6d6c2325]
stable/5.10: [5a03b42ae1ed646eb5f5acceff1fb2b1d85ec077]
stable/5.15: [0c5fd85fb01fa1a5dbb9f213b0d1925e671f30df]
stable/6.1: [9af8bb2afea3705b58fe930f97a39322f46e5b8b]
stable/6.5: [13f385f99147b4445a1ff151fabd44c12d366ab0]

CVE-2023-5345: fs/smb/client: Reset password pointer to NULL

Stable 6.1 and 6.5 was fixed.

Fixed status
mainline: [e6e43b8aa7cd3c3af686caf0c2e11819a886d705]
stable/6.1: [f555a508087ab8210b4658120ac6413d6fe2b4c7]
stable/6.5: [0c116005af551e9cf437a9ec8c80204c2d4b1b53]

CVE-2023-4244: A use-after-free vulnerability in the Linux kernel's netfilter

Stable 5.10 was fixed.

Fixed status
mainline: [5f68718b34a531a556f2f50300ead2862278da26,
f6c383b8c31a93752a52697f8430a71dcbc46adf,
  c92db3030492b8ad1d0faace7a93bbcf53850d0c,
a2dd0233cbc4d8a0abb5f64487487ffc9265beb5,
  24138933b97b055d486e8064b4a1721702442a9b,
6a33d8b73dfac0a41f3877894b38082bd0c9a5bc,
  02c6c24402bf1c1e986899c14ba22a10b510916b,
23185c6aed1ffb8fc44087880ba2767aba493779]
stable/5.10: [448be0774882f95a74fa5eb7519761152add601b,
146c76866795553dbc19998f36718d7986ad302b,
  77046cb00850e35ba935944b5100996b2ce34bba,
911dd3cdf1083f4c2e7df72aaab486a1d6dbcc0a,
  b15ea4017af82011dd55225ce77cce3d4dfc169c,
4046f2b56e5a7ba7e123ff961dd51187b8d59e78,
  dc0b1f019554e601f57e78d8f5c70e59d77e49a5,
a7653eaea0a59a6993c62d3653af5c880ce28533]
stable/6.1: [7148bca63b212fc8e5c2e8374e14cd62b1c8441c,
59dab3bf0b8fc08eb802721c0532f13dd89209b8,
  ea3eb9f2192e4fc33b795673e56c97a21987f868,
df650d6a4bf47248261b61ef6b174d7c54034d15,
  4ead4f74b3a9162b205f702d72d4a3421356dbc1,
0b9af4860a61f55cf716267b5ae5df34aacc4b39,
  41113aa5698ad7a82635bcb747d483e4458d518d,
afa584c35065051a11ae3ea3cc105b634053fcd8]

CVE-2023-4563: Use-after-free in nft_verdict_dump due to a race
between set GC and transaction

Stable 5.10 was fixed.

Fixed status
mainline: [24138933b97b055d486e8064b4a1721702442a9b,
5f68718b34a531a556f2f50300ead2862278da26,
  f6c383b8c31a93752a52697f8430a71dcbc46adf,
c92db3030492b8ad1d0faace7a93bbcf53850d0c,
  a2dd0233cbc4d8a0abb5f64487487ffc9265beb5,
6a33d8b73dfac0a41f3877894b38082bd0c9a5bc,
  02c6c24402bf1c1e986899c14ba22a10b510916b,
23185c6aed1ffb8fc44087880ba2767aba493779]
stable/5.10: [b15ea4017af82011dd55225ce77cce3d4dfc169c,
448be0774882f95a74fa5eb7519761152add601b,
  146c76866795553dbc19998f36718d7986ad302b,
77046cb00850e35ba935944b5100996b2ce34bba,
  911dd3cdf1083f4c2e7df72aaab486a1d6dbcc0a,
4046f2b56e5a7ba7e123ff961dd51187b8d59e78,
  dc0b1f019554e601f57e78d8f5c70e59d77e49a5,
a7653eaea0a59a6993c62d3653af5c880ce28533]

CVE-2023-4623: net/sched: sch_hfsc: Ensure inner classes have fsc curve

Stable 4.14 was fixed.

Fixed status
mainline: [b3d26c5702c7d6c45456326e56d2ccf3f103e60f]
stable/4.14: [3c0bd0b79733b7f628af1c967269db339eeef8d3]
stable/4.19: [7c62e0c3c6e9c9c15ead63339db6a0e158d22a66]
stable/5.10: [b08cc6c0396fd5cfaac4ca044f2282367347c062]
stable/5.15: [4cf994d3f4ff42d604fae2b461bdd5195a7dfabd]
stable/5.4: [da13749d5ff70bb033a8f35da32cfd6e88246b2f]
stable/6.1: [a1e820fc7808e42b990d224f40e9b4895503ac40]
stable/6.4: [5293f466d41d6c2eaad8b833576ea3dbee630dc2]
stable/6.5: [eb07894c51c7d6bb8d00948a3e6e7b52c791e93e]

CVE-2023-4881: netfilter: nftables: exthdr: fix 4-byte stack OOB write

Stable 5.10 was fixed.

Fixed status
mainline: [fd94d9dadee58e09b49075240fe83423eb1dcd36]
stable/5.10: [a7d86a77c33ba1c357a7504341172cc1507f0698]
stable/5.15: [1ad7b189cc1411048434e8595ffcbe7873b71082]
stable/6.1: [d9ebfc0f21377690837ebbd119e679243e0099cc]
stable/6.5: [c8f292322ff16b9a2272a67de396c09a50e09dce]

Currently tracking CVEs

CVE-2021-31615: Unencrypted Bluetooth Low Energy baseband links in
Bluetooth Core Specifications 4.0 through 5.2

There is no fix information.

CVE-2020-26556: kernel: malleable commitment Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26557: kernel: predictable Authvalue in Bluetooth Mesh
Provisioning Leads to MITM

No fix information.

CVE-2020-26559: kernel: Authvalue leak in Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26560: kernel: impersonation attack in Bluetooth Mesh Provisioning

No fix information.

Regards,
-- 
Masami Ichikawa
Cybertrust Japan Co., Ltd.

Email :masami.ichikawa@cybertrust.co.jp
      :masami.ichikawa@miraclelinux.com


^ permalink raw reply	[flat|nested] 33+ messages in thread

* [kernel-cve-report] New CVE entries this week
@ 2023-10-04 22:09 Masami Ichikawa
  0 siblings, 0 replies; 33+ messages in thread
From: Masami Ichikawa @ 2023-10-04 22:09 UTC (permalink / raw)
  To: cip-dev

Hi !

It's this week's CVE report.

This week reported 6 new CVEs and 0 updated CVEs.

* New CVEs

CVE-2023-44466: libceph: harden msgr2.1 frame segment length checks

CVSS v3 score is 8.8 HIGH.

An issue was discovered in net/ceph/messenger_v2.c in the Linux kernel
before 6.4.5. There is an integer signedness error,
leading to a buffer overflow and remote code execution via HELLO or
one of the AUTH frames. This occurs because of an
untrusted length taken from a TCP packet in ceph_decode_32.

This bug was introduced by commit cd1a677 ("libceph, ceph: implement
msgr2.1 protocol (crc and secure modes)") in 5.11-rc1.
So, 4.4, 4.14, 4.19, 5.4, and 5.10 are not affected.

Fixed status
mainline: [a282a2f10539dce2aa619e71e1817570d557fc97]
stable/5.15: [db8ca8d9b4dfce6d8cded796f0e671ef2c782613]
stable/6.1: [183c0ae4fafcdcb95c06f40c0c35a39d89c1aa2d]

CVE-2023-42754: null pointer dereference in Linux kernel ipv4 stack

CVSS v3 score is not provided.

A null pointer dereference bug was found in the
ipv4_send_dest_unreach" function in the net/ipv4/route.c.
This bug was introduced by commit ed0de45 ("ipv4: recompile ip options
in ipv4_link_failure") in 5.1-rc6.
The commit ed0de45 was backported to 4.4, 4.14, and 4.19 so these
kernels are affected as well.

To abuse this bug, an attacker requires CAP_NET_ADMIN privilege.

Fixed status
mainline: [0113d9c9d1ccc07f5a3710dac4aa24b6d711278c]

CVE-2023-4732: mm/userfaultfd: fix uffd-wp special cases for fork()

CVSS v3 score is not provided (NIST).
CVSS v3 score is 4.7 MEDIUM (CNA).

A flaw was found in the Linux Kernel's memory management subsystem. A
task exits and releases a 2MB page in a vma (vm_area_struct) and hits
the BUG statement in pfn_swap_entry_to_page() referencing pmd_t x.

This bug was introduced by commit b569a17 ("userfaultfd: wp: drop
_PAGE_UFFD_WP properly when fork") in 5.7-rc1.
The commit b569a17 is not backported to older stable kernels.

Fixed status
mainline: [8f34f1eac3820fc2722e5159acceb22545b30b0d]
stable/5.10: [9e1cf2d1ed37c934c9935f2c0b2f8b15d9355654]

CVE-2023-5345: fs/smb/client: Reset password pointer to NULL

CVSS v3 score is not provided (NIST).
CVSS v3 score is 7.8 MEDIUM (CNA).

A use-after-free vulnerability in the Linux kernel's fs/smb/client
component can be exploited to achieve local privilege escalation. In
case of an error in smb3_fs_context_parse_param, ctx->password was
freed but the field was not set to NULL which could lead to double
free.

Fixed status
mainline: [e6e43b8aa7cd3c3af686caf0c2e11819a886d705]

CVE-2023-4610: slab-use-after-free Read in radix_tree_lookup

CVSS v3 score is not provided.

A use-after-free bug was found in lib/radix-tree.c which allows a
local attacker to crash the system, and lead to kernel infomation
leak.

Fixed status
Not fixed yet

* Updated CVEs

No update CVEs this week.

Fixed status

Currently tracking CVEs

CVE-2021-31615: Unencrypted Bluetooth Low Energy baseband links in
Bluetooth Core Specifications 4.0 through 5.2

There is no fix information.

CVE-2020-26556: kernel: malleable commitment Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26557: kernel: predictable Authvalue in Bluetooth Mesh
Provisioning Leads to MITM

No fix information.

CVE-2020-26559: kernel: Authvalue leak in Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26560: kernel: impersonation attack in Bluetooth Mesh Provisioning

No fix information.

Regards,
-- 
Masami Ichikawa
Cybertrust Japan Co., Ltd.

Email :masami.ichikawa@cybertrust.co.jp
      :masami.ichikawa@miraclelinux.com


^ permalink raw reply	[flat|nested] 33+ messages in thread

* [kernel-cve-report] New CVE entries this week
@ 2023-09-27 22:58 Masami Ichikawa
  0 siblings, 0 replies; 33+ messages in thread
From: Masami Ichikawa @ 2023-09-27 22:58 UTC (permalink / raw)
  To: cip-dev

Hi !

It's this week's CVE report.

This week reported 5 new CVEs and 7 updated CVEs.

* New CVEs

CVE-2023-42753: netfilter: ipset: add the missing
IP_SET_HASH_WITH_NET0 macro for ip_set_hash_netportnet.c

CVSS v3 score is 7.8 HIGH (NIST).
CVSS v3 score is 7.0 HIGH (CNA).

An array out-of-bound access bug was found in the netfilter subsystem.
If an attacker passes crafted cidr value as 0 that causes an integer
underflow. As a result, it leads to slab oob access.

This bug was introduced by commit 886503f ("netfilter: ipset: actually
allow allowable CIDR 0 in hash:net,port,net") in 4.20-rc1. This commit
was backported to 4.19 so 4.19 also affected.

Fixed status
mainline: [050d91c03b28ca479df13dfb02bcd2c60dd6a878]
stable/4.14: [7935b636dd693dfe4483cfef4a1e91366c8103fa]
stable/4.19: [e632d09dffc68b9602d6893a99bfe3001d36cefc]
stable/5.10: [83091f8ac03f118086596f17c9a52d31d6ca94b3]
stable/5.15: [a9e6142e5f8f6ac7d1bca45c1b2b13b084ea9e14]
stable/5.4: [109e830585e89a03d554bf8ad0e668630d0a6260]
stable/6.1: [7ca0706c68adadf86a36b60dca090f5e9481e808]
stable/6.5: [d95c8420efe684b964e3aa28108e9a354bcd7225]


CVE-2023-42755: wild pointer access in rsvp classifer in the Linux kernel

CVSS v3 score is not provided.

There is a slab-out-of-bound access bug found in the net/sched
subsystem which leads Dos.
This fix removes CONFIG_NET_CLS_RSVP and NET_CLS_RSVP6 because these
features haven't been getting
much maintenance attention due to lack of known users.

Fixed status
mainline: [265b4da82dbf5df04bee5a5d46b7474b1aaf326a]
stable/4.14: [a048f77ba9cf7f77a06b2ee60446c6cc061c2daf]
stable/4.19: [6ca0ea6a46e7a2d70fb1b1f6a886efe2b2365e16]
stable/5.10: [8db844077ec9912d75952c80d76da71fc2412852]
stable/5.15: [08569c92f7f339de21b7a68d43d6795fc0aa24f2]
stable/5.4: [42900fd140c8db99141b9f083bfe8de887190ed9]
stable/6.1: [b93aeb6352b0229e3c5ca5ca4ff015b015aff33c]

CVE-2023-5158: vringh: don''t use vringh_kiov_advance() in vringh_iov_xfer()

CVSS v3 score is 5.5 MEDIUM (NIST).
CVSS v3 score is 6.5 MEDIUM (CNA).

A flaw was found in vringh_kiov_advance in drivers/vhost/vringh.c in
the host side of a virtio ring in the Linux Kernel. This issue may
result in a denial of service from guest to host via zero length
descriptor.

It was introduced by commit b8c06ad4d67d ("vringh: implement
vringh_kiov_advance()") in 5.13-rc1.

Fixed status
Patch is available on the virtualization mailing
list(https://lore.kernel.org/virtualization/20230925103057.104541-1-sgarzare@redhat.com/T/#u),
but it hasn't been merged yet.

CVE-2023-5197: netfilter: nf_tables: disallow rule removal from chain binding

CVSS v3 score is not provided (NIST).
CVSS v3 score is 7.8 HIGH (CNA).

A use-after-free vulnerability in the Linux kernel's netfilter:
nf_tables component can be exploited to achieve local privilege
escalation. Addition and removal of rules from chain bindings within
the same transaction leads to use-after-free.

This bug was introduced by commit d0e2c7d ("netfilter: nf_tables: add
NFT_CHAIN_BINDING") in 5.9-rc1.
So, 5.4, 4.19, 4.14, and 4.4 are not affected.

Fixed status
mainline: [f15f29fd4779be8a418b66e9d52979bb6d6c2325]

CVE-2023-42756: netfilter: ipset: Fix race between IPSET_CMD_CREATE
and IPSET_CMD_SWAP

CVSS v3 score is not provided.

A race condition bug was found in netfilter/ip_set subsystem. It leads
local DoS.

This bug was introduced by commit 24e2278 ("netfilter: ipset: Add
schedule point in call_ad().") in 6.4-rc6.
This commit was backported to 6.x and 5.x. However the commit is not
backported to Linux 4.x series. So, Linux 4.x is not affected.

Fixed status
mainline: [7433b6d2afd512d04398c73aa984d1e285be125b]

* Updated CVEs

CVE-2022-28796: jbd2_journal_wait_updates in fs/jbd2/transaction.c in
the Linux kernel

Stable 5.15 was fixed.

Fixed status
mainline: [cc16eecae687912238ee6efbff71ad31e2bc414e]
stable/5.15: [e9270898222ae8404f6b3738f82bc964b0dc1819]
stable/5.17: [bff94c57bd130e3062afa94414c2294871314096]

CVE-2023-4128: Use-after-free vulnerabilities in the net/sched
classifiers: cls_fw, cls_u32 and cls_route

Stable 4.14 was fixed.

Fixed status
mainline: [3044b16e7c6fe5d24b1cdbcf1bd0a9d92d1ebd81,
76e42ae831991c828cffa8c37736ebfb831ad5ec,
  b80b829e9e2c1b3f7aae34855e04d8f6ecaf13c8]
stable/4.14: [f0f874147a5b00eae875c24281531f8de7900079,
530a85ea747965b7c275fa44a364916e0ec2efaa,
  226d84d54a9339b7045aff36c8f56d6ee9270476]
stable/4.19: [4aae24015ecd70d824a953e2dc5b0ca2c4769243,
ad8f36f96696a7f1d191da66637c415959bab6d8,
  4f38dc8496d1991e2c055a0068dd98fb48affcc6]
stable/5.10: [b4256c99a7116c9514224847e8aaee2ecf110a0a,
a8d478200b104ff356f51e1f63499fe46ba8c9b8,
  aaa71c4e8ad98828ed50dde3eec8e0d545a117f7]
stable/5.15: [262430dfc618509246e07acd26211cb4cca79ecc,
9edf7955025a602ab6bcc94d923c436e160a10e3,
  79c3d81c9ad140957b081c91908d7e2964dc603f]
stable/5.4: [be785808db32b595728c4042d002c83d0dd4b66f,
83e3d4b0ae373dcba30c68bf28f8d179191a297a,
  1c8262f31fd2d23d1cfd2539715d976c2a99e582]
stable/6.1: [aab2d095ce4dd8d01ca484c0cc641fb497bf74db,
7f691439b29be0aae68f83ad5eecfddc11007724,
  d4d3b53a4c66004e8e864fea744b3a2b86a73b62]
stable/6.4: [4b717802428fa02cbcbb61209f638f65f9cd4710,
7d848d718aeb3b482e177b682dd04e76dd413afb,
  a836184b670f59e24d3a0f7c07115ec6e6ce6900]

CVE-2023-4207: net/sched: cls_fw: No longer copy tcf_result on update
to avoid use-after-free

Stable 4.14 and 4.19 were fixed.

Fixed status
mainline: [76e42ae831991c828cffa8c37736ebfb831ad5ec]
stable/4.14: [530a85ea747965b7c275fa44a364916e0ec2efaa]
stable/4.19: [4f38dc8496d1991e2c055a0068dd98fb48affcc6]
stable/5.10: [a8d478200b104ff356f51e1f63499fe46ba8c9b8]
stable/5.15: [9edf7955025a602ab6bcc94d923c436e160a10e3]
stable/5.4: [83e3d4b0ae373dcba30c68bf28f8d179191a297a]
stable/6.1: [7f691439b29be0aae68f83ad5eecfddc11007724]
stable/6.4: [7d848d718aeb3b482e177b682dd04e76dd413afb]

CVE-2023-4623: net/sched: sch_hfsc: Ensure inner classes have fsc curve

Stable 4.19 and 5.4 were fixed.

Fixed commit
mainline: [b3d26c5702c7d6c45456326e56d2ccf3f103e60f]
stable/4.19: [7c62e0c3c6e9c9c15ead63339db6a0e158d22a66]
stable/5.10: [b08cc6c0396fd5cfaac4ca044f2282367347c062]
stable/5.15: [4cf994d3f4ff42d604fae2b461bdd5195a7dfabd]
stable/5.4: [da13749d5ff70bb033a8f35da32cfd6e88246b2f]
stable/6.1: [a1e820fc7808e42b990d224f40e9b4895503ac40]
stable/6.4: [5293f466d41d6c2eaad8b833576ea3dbee630dc2]
stable/6.5: [eb07894c51c7d6bb8d00948a3e6e7b52c791e93e]

CVE-2023-4921: net: sched: sch_qfq: Fix UAF in qfq_dequeue()

Stable 4.14, 4.19, and 5.4 were fixed.

Fixed status
mainline: [8fc134fee27f2263988ae38920bc03da416b03d8]
stable/4.14: [d9f43fc5a78d1505733d3621cd4c044eaf71a02f]
stable/4.19: [7ea1faa59c75336d86893378838ed1e6f20c0520]
stable/5.10: [746a8df5e4d235059b1adf02e8456e7ec132d2d8]
stable/5.15: [6ea277b2c6263931798234e2eed892ecfbb85596]
stable/5.4: [a6d11571b91d34fd7ce8451c2dfd112194c79ae2]
stable/6.1: [a18349dc8d916a64d7c93f05da98953e3386d8e9]
stable/6.5: [e5471b82c36396e809817cb988dfc4bce0a688cb]

CVE-2023-1989: Bluetooth: btsdio: fix use after free bug in
btsdio_remove due to unfinished work

Added commit 3efcbf2 ("Bluetooth: btsdio: fix use after free bug in
btsdio_remove due to race condition") to stable/4.19.

Fixed status
mainline: [1e9ac114c4428fdb7ff4635b45d4f46017e8916f,
73f7b171b7c09139eb3c6a5677c200dc1be5f318]
stable/4.14: [95eacef5692545f199fae4e52abfbfa273acb351]
stable/4.19: [af4d48754d5517d33bac5e504ff1f1de0808e29e,
3efcbf25e5ab4d4ad1b7e6ba0869ff85540e3f6e]
stable/5.10: [da3d3fdfb4d523c5da30e35a8dd90e04f0fd8962,
746b363bef41cc159c051c47f9e30800bc6b520d]
stable/5.15: [8efae2112d910d8e5166dd0a836791b08721eef1]
stable/5.4: [a18fb433ceb56e0787546a9d77056dd0f215e762]
stable/6.1: [cbf8deacb7053ce3e3fed64b277c6c6989e65bba,
179c65828593aff1f444e15debd40a477cb23cf4]
stable/6.2: [c59c65a14e8f7d738429648833f3bb3f9df0513f]

CVE-2023-1194: use-after-free in parse_lease_state()

The mainline and stable 6.1 was fixed.

Fixed status
mainline: [fc6c6a3c324c1b3e93a03d0cfa3749c781f23de0]
stable/6.1: [8f2984233c87a1d08f4c45f077130590c7a2c991]

Currently tracking CVEs

CVE-2021-31615: Unencrypted Bluetooth Low Energy baseband links in
Bluetooth Core Specifications 4.0 through 5.2

There is no fix information.

CVE-2020-26556: kernel: malleable commitment Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26557: kernel: predictable Authvalue in Bluetooth Mesh
Provisioning Leads to MITM

No fix information.

CVE-2020-26559: kernel: Authvalue leak in Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26560: kernel: impersonation attack in Bluetooth Mesh Provisioning

No fix information.

Regards,
-- 
Masami Ichikawa
Cybertrust Japan Co., Ltd.

Email :masami.ichikawa@cybertrust.co.jp
      :masami.ichikawa@miraclelinux.com


^ permalink raw reply	[flat|nested] 33+ messages in thread

* [kernel-cve-report] New CVE entries this week
@ 2023-09-20 22:51 Masami Ichikawa
  0 siblings, 0 replies; 33+ messages in thread
From: Masami Ichikawa @ 2023-09-20 22:51 UTC (permalink / raw)
  To: cip-dev

Hi !

It's this week's CVE report.

This week reported 1 new CVEs and 6 updated CVEs.

* New CVEs

CVE-2023-42752: integer overflows in kmalloc_reserve()

CVSS v3 score is not provided .

An integer overflow bug was found in kmalloc_reserve() in
net/core/skbuff.c when calculating  memory size to allocate.
If a user passes a huge value to the size parameter, it leads to an
integer overflow bug.

This bug was introduced by commit 12d6c1d ("skbuff: Proactively round
up to kmalloc bucket size") in 6.2-rc1.
It was backported to 6.1. However, Linux 4.4, 4.14, 4.19, 5.4, 5.10
and 5.15 are not affected by this vulnerability.

Fixed status
mainline: [915d975b2ffa58a14bfcf16fafe00c41315949ff,
c3b704d4a4a265660e665df51b129e8425216ed1]
stable/6.1: [6678912b4df1bfac6f7c80642d56dc22e23419e4,
31cf7853a940181593e4472fc56f46574123f9f6]
stable/6.5: [bf7da02d2b8faf324206e1cbe64a4813ff903cc1,
3138192865c2a1f089dd27a7d80a7271ecd468e7]

* Updated CVEs

CVE-2023-4244: A use-after-free vulnerability in the Linux kernel's netfilter

Added following commits.
- 2413893 ("netfilter: nf_tables: don't skip expired elements during walk")
- 6a33d8b ("netfilter: nf_tables: fix GC transaction races with netns
and netlink event exit path")
- 02c6c24 ("netfilter: nf_tables: GC transaction race with netns dismantle")
- 23185c6 ("netfilter: nft_dynset: disallow object maps")

Fixed status
mainline: [5f68718b34a531a556f2f50300ead2862278da26,
f6c383b8c31a93752a52697f8430a71dcbc46adf,
  c92db3030492b8ad1d0faace7a93bbcf53850d0c,
a2dd0233cbc4d8a0abb5f64487487ffc9265beb5,
  24138933b97b055d486e8064b4a1721702442a9b,
6a33d8b73dfac0a41f3877894b38082bd0c9a5bc,
  02c6c24402bf1c1e986899c14ba22a10b510916b,
23185c6aed1ffb8fc44087880ba2767aba493779]

CVE-2023-1989: Bluetooth: btsdio: fix use after free bug in
btsdio_remove due to unfinished work

Added commit 746b363 ("Bluetooth: btsdio: fix use after free bug in
btsdio_remove due to race condition") to 5.10.

Fixed status
mainline: [1e9ac114c4428fdb7ff4635b45d4f46017e8916f,
73f7b171b7c09139eb3c6a5677c200dc1be5f318]
stable/4.14: [95eacef5692545f199fae4e52abfbfa273acb351]
stable/4.19: [af4d48754d5517d33bac5e504ff1f1de0808e29e]
stable/5.10: [da3d3fdfb4d523c5da30e35a8dd90e04f0fd8962,
746b363bef41cc159c051c47f9e30800bc6b520d]
stable/5.15: [8efae2112d910d8e5166dd0a836791b08721eef1]
stable/5.4: [a18fb433ceb56e0787546a9d77056dd0f215e762]
stable/6.1: [cbf8deacb7053ce3e3fed64b277c6c6989e65bba,
179c65828593aff1f444e15debd40a477cb23cf4]
stable/6.2: [c59c65a14e8f7d738429648833f3bb3f9df0513f]

CVE-2023-37453: i out-of-bounds in read_descriptors in drivers/usb/core/sysfs

Stable 5.10 and 5.15 were fixed.

Fixed status
mainline: [ff33299ec8bb80cdcc073ad9c506bd79bb2ed20b]
stable/5.10: [9d241c5d9a9b7ad95c90c6520272fe404d5ac88f]
stable/5.15: [7fe9d87996062f5eb0ca476ad0257f79bf43aaf5]
stable/6.1: [8186596a663506b1124bede9fde6f243ef9f37ee]
stable/6.4: [b4a074b1fb222164ed7d5c0b8c922dc4a0840848]
stable/6.5: [b9fbfb349eacc0820f91c797d7f0a3ac7a4935b5]

CVE-2023-4623: net/sched: sch_hfsc: Ensure inner classes have fsc curve

Stable 5.10 and 5.15 were fixed.

Fixed status
mainline: [b3d26c5702c7d6c45456326e56d2ccf3f103e60f]
stable/5.10: [b08cc6c0396fd5cfaac4ca044f2282367347c062]
stable/5.15: [4cf994d3f4ff42d604fae2b461bdd5195a7dfabd]
stable/6.1: [a1e820fc7808e42b990d224f40e9b4895503ac40]
stable/6.4: [5293f466d41d6c2eaad8b833576ea3dbee630dc2]
stable/6.5: [eb07894c51c7d6bb8d00948a3e6e7b52c791e93e]

CVE-2023-4881: netfilter: nftables: exthdr: fix 4-byte stack OOB write

Stable 5.15, 6.1, and 6.5 were fixed.

Fixed status
mainline: [fd94d9dadee58e09b49075240fe83423eb1dcd36]
stable/5.15: [1ad7b189cc1411048434e8595ffcbe7873b71082]
stable/6.1: [d9ebfc0f21377690837ebbd119e679243e0099cc]
stable/6.5: [c8f292322ff16b9a2272a67de396c09a50e09dce]

CVE-2023-4921: net: sched: sch_qfq: Fix UAF in qfq_dequeue()

Stable 5.10, 5.15, 6.1, and 6.5 were fixed.

Fixed status
mainline: [8fc134fee27f2263988ae38920bc03da416b03d8]
stable/5.10: [746a8df5e4d235059b1adf02e8456e7ec132d2d8]
stable/5.15: [6ea277b2c6263931798234e2eed892ecfbb85596]
stable/6.1: [a18349dc8d916a64d7c93f05da98953e3386d8e9]
stable/6.5: [e5471b82c36396e809817cb988dfc4bce0a688cb]

Currently tracking CVEs

CVE-2021-31615: Unencrypted Bluetooth Low Energy baseband links in
Bluetooth Core Specifications 4.0 through 5.2

There is no fix information.

CVE-2020-26556: kernel: malleable commitment Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26557: kernel: predictable Authvalue in Bluetooth Mesh
Provisioning Leads to MITM

No fix information.

CVE-2020-26559: kernel: Authvalue leak in Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26560: kernel: impersonation attack in Bluetooth Mesh Provisioning

No fix information.

Regards,
-- 
Masami Ichikawa
Cybertrust Japan Co., Ltd.

Email :masami.ichikawa@cybertrust.co.jp
      :masami.ichikawa@miraclelinux.com


^ permalink raw reply	[flat|nested] 33+ messages in thread

end of thread, other threads:[~2024-05-08 23:46 UTC | newest]

Thread overview: 33+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-03-27 23:10 [kernel-cve-report] New CVE entries this week Masami Ichikawa
  -- strict thread matches above, loose matches on Subject: below --
2024-05-08 23:45 Masami Ichikawa
2024-05-02  3:10 Masami Ichikawa
2024-04-24 22:53 Masami Ichikawa
2024-04-18  4:09 Masami Ichikawa
2024-04-11  2:21 Masami Ichikawa
2024-04-04  5:34 Masami Ichikawa
2024-03-20 23:36 Masami Ichikawa
2024-03-13 23:34 Masami Ichikawa
2024-03-07  3:08 Masami Ichikawa
2024-02-29  0:02 Masami Ichikawa
2024-02-22  0:31 Masami Ichikawa
2024-02-14 22:47 Masami Ichikawa
2024-02-07 23:05 Masami Ichikawa
2024-01-31 23:18 Masami Ichikawa
2024-01-24 23:17 Masami Ichikawa
2024-01-10 22:52 Masami Ichikawa
2024-01-03 23:09 Masami Ichikawa
2023-12-27 22:47 Masami Ichikawa
2023-12-20 23:08 Masami Ichikawa
2023-12-13 22:52 Masami Ichikawa
2023-12-06 23:22 Masami Ichikawa
2023-11-29 23:03 Masami Ichikawa
2023-11-22 23:21 Masami Ichikawa
2023-11-15 22:48 Masami Ichikawa
2023-11-08 22:55 Masami Ichikawa
2023-11-01 22:42 Masami Ichikawa
2023-10-25 23:30 Masami Ichikawa
2023-10-18 23:20 Masami Ichikawa
2023-10-11 22:54 Masami Ichikawa
2023-10-04 22:09 Masami Ichikawa
2023-09-27 22:58 Masami Ichikawa
2023-09-20 22:51 Masami Ichikawa

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.