I think this is true, with the MIT license being the most popular.
From Linus[1] on the topic of GPLv3, he chose GPLv2 as it was the best choice for doing kernel development - giving code and getting code back in return. One of his gripes about GPLv3, IIRC, was the 'Tivoization'[2] additions. He felt it was going too far the other way.
Furthermore, unlike many other projects, Linux is not licensed GPLv2 or later and doesn't have copyright assignment. This makes changing the license unilaterally at least problematic. Not necessarily impossible but, at least some would argue the permission of all the contributors would be required which would be basically impossible.
Yes, Linus himself mentioned they'd all need to be contacted and agree. He also said he saw the GPLv3 draft and so it was an early and conscious decision to not have a 'GPLv2 or later' license.
There were differences of opinion at the time. Eben Moglen said something to the effect that it could probably be relicensed on the theory that its history suggested it could be treated as a collective work. But it would have been controversial and Linus didn't want to anyway so discussions never went further than that.
From Linus[1] on the topic of GPLv3, he chose GPLv2 as it was the best choice for doing kernel development - giving code and getting code back in return. One of his gripes about GPLv3, IIRC, was the 'Tivoization'[2] additions. He felt it was going too far the other way.
[1] https://www.youtube.com/watch?v=PaKIZ7gJlRU [2] https://en.wikipedia.org/wiki/Tivoization