| Message ID | 20211125095339.GC3327@amd (mailing list archive) |
|---|---|
| State | New |
| Headers | show |
| Series | CVE-2021-3640: UAF in sco_send_frame function was Re: [cip-dev] New CVE entries in this week | expand |
Hi ! On Thu, Nov 25, 2021 at 6:53 PM Pavel Machek <pavel@denx.de> wrote: > > Hi! > > > > CVE-2021-3640: UAF in sco_send_frame function > > > > > > 5.10 and 5.15 are fixed this week. > > > > > > Fixed status > > > > > > mainline: [99c23da0eed4fd20cae8243f2b51e10e66aa0951] > > > stable/5.10: [4dfba42604f08a505f1a1efc69ec5207ea6243de] > > > stable/5.14: [2c2b295af72e4e30d17556375e100ae65ac0b896] > > > stable/5.15: [b990c219c4c9d4993ef65ea9db73d9497e70f697] > > > stable/5.4: [d416020f1a9cc5f903ae66649b2c56d9ad5256ab] > > > > Interesting. > > > > commit 99c23da0eed4fd20cae8243f2b51e10e66aa0951 > > Author: Takashi Iwai <tiwai@suse.de> > > > > Says: > > > > This should be the last piece for fixing CVE-2021-3640 after a few > > already queued fixes. > > > > Which means more than 99c23da0eed is needed to fix this one, > > unfortunately it does not give us good way to identify what commits > > are needed. > > Aha, but we have required information in > cip-kernel-sec/issues/CVE-2021-3640.yml. It lists patches that should > be fixing this. > > Some searching in the trees reveals that one of those patches is buggy > itself, and additionaly 49d8a5606428ca0962d09050a5af81461ff90fbb is > needed. > > The patches fixing this are: > > ~ stable/5.10: [4dfba42604f08a505f1a1efc69ec5207ea6243de, > f2f856b65ac4b77049c76c0e89ecd3a177e9fcd1, > 98d44b7be6f1bcfd4f824c5f8bc2b742f890879f, > c20d8c197454068da758a83e09d93683f520d681, > a1073aad497d0d071a71f61b721966a176d50c08] > > But we still miss backport of 27c24fda62b6 ("Bluetooth: switch to > lock_sock in SCO") to 5.10, which has its own prerequisites > according to the changelog. AFAICT those prerequisites are > 734bc5ff783115aa3164f4e9dd5967ae78e0a8ab and > ba316be1b6a00db7126ed9a39f9bee434a508043, and both are in 5.10. > > I'm not sure how to express this in yml cleanly. I came with this: > > diff --git a/issues/CVE-2021-3640.yml b/issues/CVE-2021-3640.yml > index fb52d5a..d386093 100644 > --- a/issues/CVE-2021-3640.yml > +++ b/issues/CVE-2021-3640.yml > @@ -23,9 +23,23 @@ comments: > there is no fixed information as of 2021/07/26. > Fixed in bluetooth-next tree. commit 99c23da0eed4fd20cae8243f2b51e10e66aa0951. > ubuntu/sbeattie: Possibly addressed by Desmond Cheong Zhi Xi's patchset. > + pavel: We are one patch away from fixing this 5.10, 27c24fda62b6 is needed. > fixed-by: > - mainline: [99c23da0eed4fd20cae8243f2b51e10e66aa0951] > - stable/5.10: [4dfba42604f08a505f1a1efc69ec5207ea6243de] > + mainline: [99c23da0eed4fd20cae8243f2b51e10e66aa0951, > + e04480920d1eec9c061841399aa6f35b6f987d8b, > + 734bc5ff783115aa3164f4e9dd5967ae78e0a8ab, > + 49d8a5606428ca0962d09050a5af81461ff90fbb, > + ba316be1b6a00db7126ed9a39f9bee434a508043, > + 27c24fda62b601d6f9ca5e992502578c4310876f, > + 734bc5ff783115aa3164f4e9dd5967ae78e0a8ab, > + ba316be1b6a00db7126ed9a39f9bee434a508043] > + stable/5.10: [4dfba42604f08a505f1a1efc69ec5207ea6243de, > + f2f856b65ac4b77049c76c0e89ecd3a177e9fcd1, > + 98d44b7be6f1bcfd4f824c5f8bc2b742f890879f, > + c20d8c197454068da758a83e09d93683f520d681, > + a1073aad497d0d071a71f61b721966a176d50c08, > + 98d44b7be6f1bcfd4f824c5f8bc2b742f890879f, > + a1073aad497d0d071a71f61b721966a176d50c08] > stable/5.14: [2c2b295af72e4e30d17556375e100ae65ac0b896] > stable/5.15: [b990c219c4c9d4993ef65ea9db73d9497e70f697] > stable/5.4: [d416020f1a9cc5f903ae66649b2c56d9ad5256ab] > Thank you for your analysis result ! I applied it. I checked 27c24fda62b601d6f9ca5e992502578c4310876f is able to apply cleanly to stable/5.10 tree or not. Unfortunately it need to fix conflicts. git-am shows following two errors. Applying: Bluetooth: switch to lock_sock in SCO Checking patch net/bluetooth/sco.c... error: while searching for: BT_DBG("sock %p state %d", sk, sk->sk_state); bh_lock_sock(sk); sk->sk_err = ETIMEDOUT; sk->sk_state_change(sk); bh_unlock_sock(sk); sco_sock_kill(sk); sock_put(sk); error: patch failed: net/bluetooth/sco.c:93 error: while searching for: if (sk) { sock_hold(sk); bh_lock_sock(sk); sco_sock_clear_timer(sk); sco_chan_del(sk, err); bh_unlock_sock(sk); sco_sock_kill(sk); sock_put(sk); error: patch failed: net/bluetooth/sco.c:193 > Best regards, > Pavel > -- > DENX Software Engineering GmbH, Managing Director: Wolfgang Denk > HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany > > -=-=-=-=-=-=-=-=-=-=-=- > Links: You receive all messages sent to this group. > View/Reply Online (#7015): https://lists.cip-project.org/g/cip-dev/message/7015 > Mute This Topic: https://lists.cip-project.org/mt/87299556/4520416 > Group Owner: cip-dev+owner@lists.cip-project.org > Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129101/4520416/1465703922/xyzzy [masami.ichikawa@miraclelinux.com] > -=-=-=-=-=-=-=-=-=-=-=- > Regards,
Hi! > > > Interesting. > > > > > > commit 99c23da0eed4fd20cae8243f2b51e10e66aa0951 > > > Author: Takashi Iwai <tiwai@suse.de> > > > > > > Says: > > > > > > This should be the last piece for fixing CVE-2021-3640 after a few > > > already queued fixes. > > > > > > Which means more than 99c23da0eed is needed to fix this one, > > > unfortunately it does not give us good way to identify what commits > > > are needed. > > > > Aha, but we have required information in > > cip-kernel-sec/issues/CVE-2021-3640.yml. It lists patches that should > > be fixing this. > > > > Some searching in the trees reveals that one of those patches is buggy > > itself, and additionaly 49d8a5606428ca0962d09050a5af81461ff90fbb is > > needed. > > > > The patches fixing this are: > > > > ~ stable/5.10: [4dfba42604f08a505f1a1efc69ec5207ea6243de, > > f2f856b65ac4b77049c76c0e89ecd3a177e9fcd1, > > 98d44b7be6f1bcfd4f824c5f8bc2b742f890879f, > > c20d8c197454068da758a83e09d93683f520d681, > > a1073aad497d0d071a71f61b721966a176d50c08] > > > > But we still miss backport of 27c24fda62b6 ("Bluetooth: switch to > > lock_sock in SCO") to 5.10, which has its own prerequisites > > according to the changelog. AFAICT those prerequisites are > > 734bc5ff783115aa3164f4e9dd5967ae78e0a8ab and > > ba316be1b6a00db7126ed9a39f9bee434a508043, and both are in 5.10. > > > > I'm not sure how to express this in yml cleanly. I came with this: > > > > diff --git a/issues/CVE-2021-3640.yml b/issues/CVE-2021-3640.yml > > index fb52d5a..d386093 100644 > > --- a/issues/CVE-2021-3640.yml > > +++ b/issues/CVE-2021-3640.yml > > @@ -23,9 +23,23 @@ comments: > > there is no fixed information as of 2021/07/26. > > Fixed in bluetooth-next tree. commit 99c23da0eed4fd20cae8243f2b51e10e66aa0951. > > ubuntu/sbeattie: Possibly addressed by Desmond Cheong Zhi Xi's patchset. > > + pavel: We are one patch away from fixing this 5.10, 27c24fda62b6 is needed. > > fixed-by: > > - mainline: [99c23da0eed4fd20cae8243f2b51e10e66aa0951] > > - stable/5.10: [4dfba42604f08a505f1a1efc69ec5207ea6243de] > > + mainline: [99c23da0eed4fd20cae8243f2b51e10e66aa0951, > > + e04480920d1eec9c061841399aa6f35b6f987d8b, > > + 734bc5ff783115aa3164f4e9dd5967ae78e0a8ab, > > + 49d8a5606428ca0962d09050a5af81461ff90fbb, > > + ba316be1b6a00db7126ed9a39f9bee434a508043, > > + 27c24fda62b601d6f9ca5e992502578c4310876f, > > + 734bc5ff783115aa3164f4e9dd5967ae78e0a8ab, > > + ba316be1b6a00db7126ed9a39f9bee434a508043] > > + stable/5.10: [4dfba42604f08a505f1a1efc69ec5207ea6243de, > > + f2f856b65ac4b77049c76c0e89ecd3a177e9fcd1, > > + 98d44b7be6f1bcfd4f824c5f8bc2b742f890879f, > > + c20d8c197454068da758a83e09d93683f520d681, > > + a1073aad497d0d071a71f61b721966a176d50c08, > > + 98d44b7be6f1bcfd4f824c5f8bc2b742f890879f, > > + a1073aad497d0d071a71f61b721966a176d50c08] > > stable/5.14: [2c2b295af72e4e30d17556375e100ae65ac0b896] > > stable/5.15: [b990c219c4c9d4993ef65ea9db73d9497e70f697] > > stable/5.4: [d416020f1a9cc5f903ae66649b2c56d9ad5256ab] > > > > Thank you for your analysis result ! I applied it. > > I checked 27c24fda62b601d6f9ca5e992502578c4310876f is able to apply > cleanly to stable/5.10 tree or not. Unfortunately it need to fix > conflicts. git-am shows following two errors. As far as I can tell, logic is quite simple there and the patch would look like this. Whether the final result works and closes the security hole is different question. Best regards, Pavel commit e077740ddfa22385d53700898ea325068ca4cc6b Author: Pavel Machek <pavel@ucw.cz> Date: Thu Nov 25 14:14:04 2021 +0100 Cherry pick 27c24fda62b6 ("Bluetooth: switch to lock_sock in SCO") to close CVE-2021-3640. diff --git a/net/bluetooth/sco.c b/net/bluetooth/sco.c index 2f2b8ddc4dd5..cf165b0d15f2 100644 --- a/net/bluetooth/sco.c +++ b/net/bluetooth/sco.c @@ -93,10 +93,10 @@ static void sco_sock_timeout(struct work_struct *work) BT_DBG("sock %p state %d", sk, sk->sk_state); - bh_lock_sock(sk); + lock_sock(sk); sk->sk_err = ETIMEDOUT; sk->sk_state_change(sk); - bh_unlock_sock(sk); + release_sock(sk); sock_put(sk); } @@ -193,10 +193,10 @@ static void sco_conn_del(struct hci_conn *hcon, int err) if (sk) { sock_hold(sk); - bh_lock_sock(sk); + lock_sock(sk); sco_sock_clear_timer(sk); sco_chan_del(sk, err); - bh_unlock_sock(sk); + release_sock(sk); sock_put(sk); } @@ -1108,10 +1108,10 @@ static void sco_conn_ready(struct sco_conn *conn) if (sk) { sco_sock_clear_timer(sk); - bh_lock_sock(sk); + lock_sock(sk); sk->sk_state = BT_CONNECTED; sk->sk_state_change(sk); - bh_unlock_sock(sk); + release_sock(sk); } else { sco_conn_lock(conn); @@ -1126,12 +1126,12 @@ static void sco_conn_ready(struct sco_conn *conn) return; } - bh_lock_sock(parent); + lock_sock(parent); sk = sco_sock_alloc(sock_net(parent), NULL, BTPROTO_SCO, GFP_ATOMIC, 0); if (!sk) { - bh_unlock_sock(parent); + release_sock(parent); sco_conn_unlock(conn); return; } @@ -1152,7 +1152,7 @@ static void sco_conn_ready(struct sco_conn *conn) /* Wake up parent */ parent->sk_data_ready(parent); - bh_unlock_sock(parent); + release_sock(parent); sco_conn_unlock(conn); }
Hi ! On Fri, Nov 26, 2021 at 7:03 PM Pavel Machek <pavel@denx.de> wrote: > > Hi! > > > > Interesting. > > > > > > > > commit 99c23da0eed4fd20cae8243f2b51e10e66aa0951 > > > > Author: Takashi Iwai <tiwai@suse.de> > > > > > > > > Says: > > > > > > > > This should be the last piece for fixing CVE-2021-3640 after a few > > > > already queued fixes. > > > > > > > > Which means more than 99c23da0eed is needed to fix this one, > > > > unfortunately it does not give us good way to identify what commits > > > > are needed. > > > > > > Aha, but we have required information in > > > cip-kernel-sec/issues/CVE-2021-3640.yml. It lists patches that should > > > be fixing this. > > > > > > Some searching in the trees reveals that one of those patches is buggy > > > itself, and additionaly 49d8a5606428ca0962d09050a5af81461ff90fbb is > > > needed. > > > > > > The patches fixing this are: > > > > > > ~ stable/5.10: [4dfba42604f08a505f1a1efc69ec5207ea6243de, > > > f2f856b65ac4b77049c76c0e89ecd3a177e9fcd1, > > > 98d44b7be6f1bcfd4f824c5f8bc2b742f890879f, > > > c20d8c197454068da758a83e09d93683f520d681, > > > a1073aad497d0d071a71f61b721966a176d50c08] > > > > > > But we still miss backport of 27c24fda62b6 ("Bluetooth: switch to > > > lock_sock in SCO") to 5.10, which has its own prerequisites > > > according to the changelog. AFAICT those prerequisites are > > > 734bc5ff783115aa3164f4e9dd5967ae78e0a8ab and > > > ba316be1b6a00db7126ed9a39f9bee434a508043, and both are in 5.10. > > > > > > I'm not sure how to express this in yml cleanly. I came with this: > > > > > > diff --git a/issues/CVE-2021-3640.yml b/issues/CVE-2021-3640.yml > > > index fb52d5a..d386093 100644 > > > --- a/issues/CVE-2021-3640.yml > > > +++ b/issues/CVE-2021-3640.yml > > > @@ -23,9 +23,23 @@ comments: > > > there is no fixed information as of 2021/07/26. > > > Fixed in bluetooth-next tree. commit 99c23da0eed4fd20cae8243f2b51e10e66aa0951. > > > ubuntu/sbeattie: Possibly addressed by Desmond Cheong Zhi Xi's patchset. > > > + pavel: We are one patch away from fixing this 5.10, 27c24fda62b6 is needed. > > > fixed-by: > > > - mainline: [99c23da0eed4fd20cae8243f2b51e10e66aa0951] > > > - stable/5.10: [4dfba42604f08a505f1a1efc69ec5207ea6243de] > > > + mainline: [99c23da0eed4fd20cae8243f2b51e10e66aa0951, > > > + e04480920d1eec9c061841399aa6f35b6f987d8b, > > > + 734bc5ff783115aa3164f4e9dd5967ae78e0a8ab, > > > + 49d8a5606428ca0962d09050a5af81461ff90fbb, > > > + ba316be1b6a00db7126ed9a39f9bee434a508043, > > > + 27c24fda62b601d6f9ca5e992502578c4310876f, > > > + 734bc5ff783115aa3164f4e9dd5967ae78e0a8ab, > > > + ba316be1b6a00db7126ed9a39f9bee434a508043] > > > + stable/5.10: [4dfba42604f08a505f1a1efc69ec5207ea6243de, > > > + f2f856b65ac4b77049c76c0e89ecd3a177e9fcd1, > > > + 98d44b7be6f1bcfd4f824c5f8bc2b742f890879f, > > > + c20d8c197454068da758a83e09d93683f520d681, > > > + a1073aad497d0d071a71f61b721966a176d50c08, > > > + 98d44b7be6f1bcfd4f824c5f8bc2b742f890879f, > > > + a1073aad497d0d071a71f61b721966a176d50c08] > > > stable/5.14: [2c2b295af72e4e30d17556375e100ae65ac0b896] > > > stable/5.15: [b990c219c4c9d4993ef65ea9db73d9497e70f697] > > > stable/5.4: [d416020f1a9cc5f903ae66649b2c56d9ad5256ab] > > > > > > > Thank you for your analysis result ! I applied it. > > > > I checked 27c24fda62b601d6f9ca5e992502578c4310876f is able to apply > > cleanly to stable/5.10 tree or not. Unfortunately it need to fix > > conflicts. git-am shows following two errors. > > As far as I can tell, logic is quite simple there and the patch would > look like this. Whether the final result works and closes the security > hole is different question. > Thank you for the patch ! Yes, applying code and works properly is different question. however, your patch is LGTM. > Best regards, > Pavel > commit e077740ddfa22385d53700898ea325068ca4cc6b > Author: Pavel Machek <pavel@ucw.cz> > Date: Thu Nov 25 14:14:04 2021 +0100 > > Cherry pick 27c24fda62b6 ("Bluetooth: switch to lock_sock in SCO") to > close CVE-2021-3640. > > diff --git a/net/bluetooth/sco.c b/net/bluetooth/sco.c > index 2f2b8ddc4dd5..cf165b0d15f2 100644 > --- a/net/bluetooth/sco.c > +++ b/net/bluetooth/sco.c > @@ -93,10 +93,10 @@ static void sco_sock_timeout(struct work_struct *work) > > BT_DBG("sock %p state %d", sk, sk->sk_state); > > - bh_lock_sock(sk); > + lock_sock(sk); > sk->sk_err = ETIMEDOUT; > sk->sk_state_change(sk); > - bh_unlock_sock(sk); > + release_sock(sk); > > sock_put(sk); > } > @@ -193,10 +193,10 @@ static void sco_conn_del(struct hci_conn *hcon, int err) > > if (sk) { > sock_hold(sk); > - bh_lock_sock(sk); > + lock_sock(sk); > sco_sock_clear_timer(sk); > sco_chan_del(sk, err); > - bh_unlock_sock(sk); > + release_sock(sk); > sock_put(sk); > } > > @@ -1108,10 +1108,10 @@ static void sco_conn_ready(struct sco_conn *conn) > > if (sk) { > sco_sock_clear_timer(sk); > - bh_lock_sock(sk); > + lock_sock(sk); > sk->sk_state = BT_CONNECTED; > sk->sk_state_change(sk); > - bh_unlock_sock(sk); > + release_sock(sk); > } else { > sco_conn_lock(conn); > > @@ -1126,12 +1126,12 @@ static void sco_conn_ready(struct sco_conn *conn) > return; > } > > - bh_lock_sock(parent); > + lock_sock(parent); > > sk = sco_sock_alloc(sock_net(parent), NULL, > BTPROTO_SCO, GFP_ATOMIC, 0); > if (!sk) { > - bh_unlock_sock(parent); > + release_sock(parent); > sco_conn_unlock(conn); > return; > } > @@ -1152,7 +1152,7 @@ static void sco_conn_ready(struct sco_conn *conn) > /* Wake up parent */ > parent->sk_data_ready(parent); > > - bh_unlock_sock(parent); > + release_sock(parent); > > sco_conn_unlock(conn); > } > > > -- > DENX Software Engineering GmbH, Managing Director: Wolfgang Denk > HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany > > -=-=-=-=-=-=-=-=-=-=-=- > Links: You receive all messages sent to this group. > View/Reply Online (#7021): https://lists.cip-project.org/g/cip-dev/message/7021 > Mute This Topic: https://lists.cip-project.org/mt/87299556/4520416 > Group Owner: cip-dev+owner@lists.cip-project.org > Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129101/4520416/1465703922/xyzzy [masami.ichikawa@miraclelinux.com] > -=-=-=-=-=-=-=-=-=-=-=- > Regards,
diff --git a/issues/CVE-2021-3640.yml b/issues/CVE-2021-3640.yml index fb52d5a..d386093 100644 --- a/issues/CVE-2021-3640.yml +++ b/issues/CVE-2021-3640.yml @@ -23,9 +23,23 @@ comments: there is no fixed information as of 2021/07/26. Fixed in bluetooth-next tree. commit 99c23da0eed4fd20cae8243f2b51e10e66aa0951. ubuntu/sbeattie: Possibly addressed by Desmond Cheong Zhi Xi's patchset. + pavel: We are one patch away from fixing this 5.10, 27c24fda62b6 is needed. fixed-by: - mainline: [99c23da0eed4fd20cae8243f2b51e10e66aa0951] - stable/5.10: [4dfba42604f08a505f1a1efc69ec5207ea6243de] + mainline: [99c23da0eed4fd20cae8243f2b51e10e66aa0951, + e04480920d1eec9c061841399aa6f35b6f987d8b, + 734bc5ff783115aa3164f4e9dd5967ae78e0a8ab, + 49d8a5606428ca0962d09050a5af81461ff90fbb, + ba316be1b6a00db7126ed9a39f9bee434a508043, + 27c24fda62b601d6f9ca5e992502578c4310876f, + 734bc5ff783115aa3164f4e9dd5967ae78e0a8ab, + ba316be1b6a00db7126ed9a39f9bee434a508043] + stable/5.10: [4dfba42604f08a505f1a1efc69ec5207ea6243de, + f2f856b65ac4b77049c76c0e89ecd3a177e9fcd1, + 98d44b7be6f1bcfd4f824c5f8bc2b742f890879f, + c20d8c197454068da758a83e09d93683f520d681, + a1073aad497d0d071a71f61b721966a176d50c08, + 98d44b7be6f1bcfd4f824c5f8bc2b742f890879f, + a1073aad497d0d071a71f61b721966a176d50c08] stable/5.14: [2c2b295af72e4e30d17556375e100ae65ac0b896] stable/5.15: [b990c219c4c9d4993ef65ea9db73d9497e70f697] stable/5.4: [d416020f1a9cc5f903ae66649b2c56d9ad5256ab]