Към съдържанието
Търсене

CVE-2026-98070: Linux

8.1

CVSS 3.1

Няма данни

Вероятност да бъде експлоатирана в следващите 30 дни (EPSS)

Няма потвърждение

Атакува се

Няма данни

Време до експлоатация

Атакува се по мрежата, при специфични условия, без вход и без действие от потребителя.

    Описание

    Оригинално описание

    In the Linux kernel, the following vulnerability has been resolved: net/rds: acquire RDS_IN_XMIT in rds_tcp_reset_callbacks() rds_tcp_reset_callbacks() quiesces the transmit path by setting the path state to RDS_CONN_RESETTING and then waiting for RDS_IN_XMIT to be sampled clear before swapping the underlying socket and calling rds_send_path_reset(). Sampling the bit clear is not the same as owning it: rds_send_xmit() can re-acquire RDS_IN_XMIT right after the wait_event() returns. Its state recheck after taking the lock is a store-buffering pattern (the resetter writes the state and reads the bit, the sender writes the bit and reads the state) and acquire_in_xmit() is only an acquire operation, so on weakly ordered architectures both sides can miss each other's write and the transmit path then runs concurrently with rds_send_path_reset() rewriting cp_xmit_* state - which is exactly what the comment above rds_send_path_reset() tells its callers to prevent. Take the lock instead, hold it across the socket swap and rds_send_path_reset(), and release it with a wake-up at the end. The lock-ordering constraint documented above the wait still holds: the lock is acquired before lock_sock(), so a sender inside tcp_sendmsg() can never be waited on while we hold the socket lock. Two details of the old code go away with the same change: - t_sock is now read only after the lock is acquired. The old code cached it before waiting; the teardown in rds_conn_shutdown() releases that socket and clears t_sock, so a pointer cached before the wait can be stale by the time the accept path resumes. Reading it under RDS_IN_XMIT is what makes the exclusion complete once the teardown owns the same lock, which the next patch arranges; until then the teardown still only samples the bit, and the two paths remain as exposed to each other as they are today. - The old !osock early path called rds_send_path_reset() with no serialization at all. It now runs unde

    Засегнати продукти

    • Linux Linux: 335b48d980f631fbc5b233cbb3625ac0c86d67cb преди 670af4e4a4de5e6bb5daee3838485571a0caa5fa; 335b48d980f631fbc5b233cbb3625ac0c86d67cb преди 830a2e21b200c6b6fdccc63dd3f23932bf7a894b; 335b48d980f631fbc5b233cbb3625ac0c86d67cb преди a05790cb4ff03f797d76906990b148d83f63e7a3; 335b48d980f631fbc5b233cbb3625ac0c86d67cb преди d184e6dd4b8f3c20c018595fd09795a66b46c8ef; 335b48d980f631fbc5b233cbb3625ac0c86d67cb преди d625112564c3e980e02504270222b49b82690cee; 335b48d980f631fbc5b233cbb3625ac0c86d67cb преди 8e4c3b7844c906c7097b4cfedd9dd1f48c9a6a92; 335b48d980f631fbc5b233cbb3625ac0c86d67cb преди 062d9e008c67289e8e1b221ecdd8f9d60566d012; 335b48d980f631fbc5b233cbb3625ac0c86d67cb преди 02c5f9dc2efd823e061954d564ce00bacd1bebeb
    • Linux Linux: 4.7; преди 4.7; 5.10.271 до 5.10.*; 5.15.222 до 5.15.*; 6.1.189 до 6.1.*; 6.6.158 до 6.6.*; 6.12.111 до 6.12.*; 6.18.53 до 6.18.*; 7.2.7 до 7.2.*; от 7.3 нататък

    История

    • 25 септември 2026 Публикувано

    Други уязвимости в Linux Linux

    Първоизточници

    CVE-2026-98070: Linux | freedomonline.bg