{"api_version":"1","generated_at":"2026-08-22T21:53:00+00:00","cve":"CVE-2026-74666","urls":{"html":"https://cve.report/CVE-2026-74666","api":"https://cve.report/api/cve/CVE-2026-74666.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-74666","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-74666"},"summary":{"title":"packet: synchronize pressure clearing with ring reconfiguration","description":"In the Linux kernel, the following vulnerability has been resolved:\n\npacket: synchronize pressure clearing with ring reconfiguration\n\npacket_set_ring() updates the RX ring state under sk_receive_queue.lock,\nbut used to publish the tpacket receive mode through po->prot_hook.func\nafter releasing that lock. packet_poll() and packet_recvmsg() can then\nrun the pressure clearing path after the ring has been cleared while\nstill seeing tpacket_rcv, causing __packet_rcv_has_room() to dereference\nstale or NULL ring storage.\n\nMove the existing receive hook assignment into the same\nsk_receive_queue.lock section as the ring state update. Keep the\nassignment otherwise unchanged, including on TX ring reconfiguration, to\navoid adding behavior changes that are not required for the fix.\n\nSerialize packet_recvmsg() pressure clearing with the same queue lock\nonly after PACKET_SOCK_PRESSURE has been observed. If the flag is clear\nand the socket has moved away from tpacket_rcv, packet_set_ring() has\nalready detached the socket and waited for synchronize_net(), so no new\npacket input can set the flag again.\n\npacket_poll() already holds sk_receive_queue.lock, so it uses the new\nunlocked helper directly.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-08-22 16:16:40","updated_at":"2026-08-22 16:16:40"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/1a35da325cac4d5bcad76a2aa943408a6f1d9000","name":"https://git.kernel.org/stable/c/1a35da325cac4d5bcad76a2aa943408a6f1d9000","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/cf8189b82bb93f219ab740e0346c919ad65ada62","name":"https://git.kernel.org/stable/c/cf8189b82bb93f219ab740e0346c919ad65ada62","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/ad740b4990347521f0db260d381f9f74e7b340ba","name":"https://git.kernel.org/stable/c/ad740b4990347521f0db260d381f9f74e7b340ba","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/2c7b5eb87b2b288cdbde825f21d2b83b2f5da747","name":"https://git.kernel.org/stable/c/2c7b5eb87b2b288cdbde825f21d2b83b2f5da747","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/a08196c3cc105947746ec21309edfbb60275fcdb","name":"https://git.kernel.org/stable/c/a08196c3cc105947746ec21309edfbb60275fcdb","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-74666","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74666","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 2ccdbaa6d55b0656244ba57c4b56765a0af76c0a cf8189b82bb93f219ab740e0346c919ad65ada62 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 2ccdbaa6d55b0656244ba57c4b56765a0af76c0a ad740b4990347521f0db260d381f9f74e7b340ba git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 2ccdbaa6d55b0656244ba57c4b56765a0af76c0a 2c7b5eb87b2b288cdbde825f21d2b83b2f5da747 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 2ccdbaa6d55b0656244ba57c4b56765a0af76c0a a08196c3cc105947746ec21309edfbb60275fcdb git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 2ccdbaa6d55b0656244ba57c4b56765a0af76c0a 1a35da325cac4d5bcad76a2aa943408a6f1d9000 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 4.2","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 4.2 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.6.152 6.6.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.104 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.45 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1.9 7.1.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["net/packet/af_packet.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"cf8189b82bb93f219ab740e0346c919ad65ada62","status":"affected","version":"2ccdbaa6d55b0656244ba57c4b56765a0af76c0a","versionType":"git"},{"lessThan":"ad740b4990347521f0db260d381f9f74e7b340ba","status":"affected","version":"2ccdbaa6d55b0656244ba57c4b56765a0af76c0a","versionType":"git"},{"lessThan":"2c7b5eb87b2b288cdbde825f21d2b83b2f5da747","status":"affected","version":"2ccdbaa6d55b0656244ba57c4b56765a0af76c0a","versionType":"git"},{"lessThan":"a08196c3cc105947746ec21309edfbb60275fcdb","status":"affected","version":"2ccdbaa6d55b0656244ba57c4b56765a0af76c0a","versionType":"git"},{"lessThan":"1a35da325cac4d5bcad76a2aa943408a6f1d9000","status":"affected","version":"2ccdbaa6d55b0656244ba57c4b56765a0af76c0a","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["net/packet/af_packet.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"4.2"},{"lessThan":"4.2","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.6.*","status":"unaffected","version":"6.6.152","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.104","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.45","versionType":"semver"},{"lessThanOrEqual":"7.1.*","status":"unaffected","version":"7.1.9","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.2","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.6.152","versionStartIncluding":"4.2","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.104","versionStartIncluding":"4.2","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.45","versionStartIncluding":"4.2","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1.9","versionStartIncluding":"4.2","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2","versionStartIncluding":"4.2","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\npacket: synchronize pressure clearing with ring reconfiguration\n\npacket_set_ring() updates the RX ring state under sk_receive_queue.lock,\nbut used to publish the tpacket receive mode through po->prot_hook.func\nafter releasing that lock. packet_poll() and packet_recvmsg() can then\nrun the pressure clearing path after the ring has been cleared while\nstill seeing tpacket_rcv, causing __packet_rcv_has_room() to dereference\nstale or NULL ring storage.\n\nMove the existing receive hook assignment into the same\nsk_receive_queue.lock section as the ring state update. Keep the\nassignment otherwise unchanged, including on TX ring reconfiguration, to\navoid adding behavior changes that are not required for the fix.\n\nSerialize packet_recvmsg() pressure clearing with the same queue lock\nonly after PACKET_SOCK_PRESSURE has been observed. If the flag is clear\nand the socket has moved away from tpacket_rcv, packet_set_ring() has\nalready detached the socket and waited for synchronize_net(), so no new\npacket input can set the flag again.\n\npacket_poll() already holds sk_receive_queue.lock, so it uses the new\nunlocked helper directly."}],"providerMetadata":{"dateUpdated":"2026-08-22T15:32:38.098Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/cf8189b82bb93f219ab740e0346c919ad65ada62"},{"url":"https://git.kernel.org/stable/c/ad740b4990347521f0db260d381f9f74e7b340ba"},{"url":"https://git.kernel.org/stable/c/2c7b5eb87b2b288cdbde825f21d2b83b2f5da747"},{"url":"https://git.kernel.org/stable/c/a08196c3cc105947746ec21309edfbb60275fcdb"},{"url":"https://git.kernel.org/stable/c/1a35da325cac4d5bcad76a2aa943408a6f1d9000"}],"title":"packet: synchronize pressure clearing with ring reconfiguration","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-74666","datePublished":"2026-08-22T15:32:38.098Z","dateReserved":"2026-08-15T05:44:03.924Z","dateUpdated":"2026-08-22T15:32:38.098Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-08-22 16:16:40","lastModifiedDate":"2026-08-22 16:16:40","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"74666","Ordinal":"1","Title":"packet: synchronize pressure clearing with ring reconfiguration","CVE":"CVE-2026-74666","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"74666","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\npacket: synchronize pressure clearing with ring reconfiguration\n\npacket_set_ring() updates the RX ring state under sk_receive_queue.lock,\nbut used to publish the tpacket receive mode through po->prot_hook.func\nafter releasing that lock. packet_poll() and packet_recvmsg() can then\nrun the pressure clearing path after the ring has been cleared while\nstill seeing tpacket_rcv, causing __packet_rcv_has_room() to dereference\nstale or NULL ring storage.\n\nMove the existing receive hook assignment into the same\nsk_receive_queue.lock section as the ring state update. Keep the\nassignment otherwise unchanged, including on TX ring reconfiguration, to\navoid adding behavior changes that are not required for the fix.\n\nSerialize packet_recvmsg() pressure clearing with the same queue lock\nonly after PACKET_SOCK_PRESSURE has been observed. If the flag is clear\nand the socket has moved away from tpacket_rcv, packet_set_ring() has\nalready detached the socket and waited for synchronize_net(), so no new\npacket input can set the flag again.\n\npacket_poll() already holds sk_receive_queue.lock, so it uses the new\nunlocked helper directly.","Type":"Description","Title":"packet: synchronize pressure clearing with ring reconfiguration"}]}}}