目標達成 すべての支援者に感謝 — 100%達成しました!

目標: 1000 CNY · 調達済み: 1000 CNY

100.0%

CVE-2024-26803— Linux kernel 安全漏洞

EPSS 0.02% · P4
新しい脆弱性情報の通知を購読するログインして購読

I. CVE-2024-26803の基本情報

脆弱性情報

脆弱性についてご質問がありますか?Shenlongの分析が参考になるかご確認ください!
Shenlongの10の質問を表示 ↗

高度な大規模言語モデル技術を使用していますが、出力には不正確または古い情報が含まれる可能性があります。Shenlongはデータの正確性を確保するよう努めていますが、実際の状況に基づいて検証・判断してください。

脆弱性タイトル
net: veth: clear GRO when clearing XDP even when down
ソース: NVD (National Vulnerability Database)
脆弱性説明
In the Linux kernel, the following vulnerability has been resolved: net: veth: clear GRO when clearing XDP even when down veth sets NETIF_F_GRO automatically when XDP is enabled, because both features use the same NAPI machinery. The logic to clear NETIF_F_GRO sits in veth_disable_xdp() which is called both on ndo_stop and when XDP is turned off. To avoid the flag from being cleared when the device is brought down, the clearing is skipped when IFF_UP is not set. Bringing the device down should indeed not modify its features. Unfortunately, this means that clearing is also skipped when XDP is disabled _while_ the device is down. And there's nothing on the open path to bring the device features back into sync. IOW if user enables XDP, disables it and then brings the device up we'll end up with a stray GRO flag set but no NAPI instances. We don't depend on the GRO flag on the datapath, so the datapath won't crash. We will crash (or hang), however, next time features are sync'ed (either by user via ethtool or peer changing its config). The GRO flag will go away, and veth will try to disable the NAPIs. But the open path never created them since XDP was off, the GRO flag was a stray. If NAPI was initialized before we'll hang in napi_disable(). If it never was we'll crash trying to stop uninitialized hrtimer. Move the GRO flag updates to the XDP enable / disable paths, instead of mixing them with the ndo_open / ndo_close paths.
ソース: NVD (National Vulnerability Database)
CVSS情報
N/A
ソース: NVD (National Vulnerability Database)
脆弱性タイプ
N/A
ソース: NVD (National Vulnerability Database)
脆弱性タイトル
Linux kernel 安全漏洞
ソース: CNNVD (China National Vulnerability Database)
脆弱性説明
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel 存在安全漏洞,该漏洞源于 net veth 中存在安全问题。
ソース: CNNVD (China National Vulnerability Database)
CVSS情報
N/A
ソース: CNNVD (China National Vulnerability Database)
脆弱性タイプ
N/A
ソース: CNNVD (China National Vulnerability Database)

影響を受ける製品

ベンダープロダクト影響を受けるバージョンCPE購読
LinuxLinux d3256efd8e8b234a6251e4d4580bd2c3c31fdc4c ~ f011c103e654d83dc85f057a7d1bd0960d02831c -
LinuxLinux 5.13 -

II. CVE-2024-26803の公開POC

#POC説明ソースリンクShenlongリンク
AI生成POCプレミアム

公開POCは見つかりませんでした。

ログインしてAI POCを生成

III. CVE-2024-26803のインテリジェンス情報

登录查看更多情报信息。

Same Patch Batch · Linux · 2024-04-04 · 32 CVEs total

CVE-2024-26792btrfs: fix double free of anonymous device after snapshot creation failure
CVE-2024-26809netfilter: nft_set_pipapo: release elements in clone only from destroy path
CVE-2024-26808netfilter: nft_chain_filter: handle NETDEV_UNREGISTER for inet/ingress basechain
CVE-2024-26807spi: cadence-qspi: fix pointer reference in runtime PM hooks
CVE-2024-26806spi: cadence-qspi: remove system-wide suspend helper calls from runtime PM hooks
CVE-2024-26805netlink: Fix kernel-infoleak-after-free in __skb_datagram_iter
CVE-2024-26804net: ip_tunnel: prevent perpetual headroom growth
CVE-2024-26802stmmac: Clear variable when destroying workqueue
CVE-2024-26800tls: fix use-after-free on failed backlog decryption
CVE-2024-26801Bluetooth: Avoid potential use-after-free in hci_error_reset
CVE-2024-26799ASoC: qcom: Fix uninitialized pointer dmactl
CVE-2024-26798fbcon: always restore the old font data in fbcon_do_set_font()
CVE-2024-26797drm/amd/display: Prevent potential buffer overflow in map_hw_resources
CVE-2024-26796drivers: perf: ctr_get_width function for legacy is not defined
CVE-2024-26795riscv: Sparse-Memory/vmemmap out-of-bounds fix
CVE-2024-26793gtp: fix use-after-free and null-ptr-deref in gtp_newlink()
CVE-2024-26745powerpc/pseries/iommu: IOMMU table is not initialized for kdump over SR-IOV
CVE-2024-26791btrfs: dev-replace: properly validate device names
CVE-2024-26790dmaengine: fsl-qdma: fix SoC may hang on 16 byte unaligned read
CVE-2024-26789crypto: arm64/neonbs - fix out-of-bounds access on short input

Showing 20 of 32 CVEs. View all on vendor page →

IV. 関連脆弱性

V. CVE-2024-26803へのコメント

まだコメントはありません


コメントを残す