Skip to content
By using Twitter’s services you agree to our Cookies Use. We and our partners operate globally and use cookies, including for analytics, personalisation, and ads.

For the best Twitter experience, please use Microsoft Edge, or install the Twitter app from Microsoft Store.

  • Home Home Home, current page.
  • About

Saved searches

  • Remove
  • In this conversation
    Verified accountProtected Tweets @
Suggested users
  • Verified accountProtected Tweets @
  • Verified accountProtected Tweets @
  • Language: English
    • Bahasa Indonesia
    • Bahasa Melayu
    • Català
    • Čeština
    • Dansk
    • Deutsch
    • English UK
    • Español
    • Filipino
    • Français
    • Hrvatski
    • Italiano
    • Magyar
    • Nederlands
    • Norsk
    • Polski
    • Português
    • Română
    • Slovenčina
    • Suomi
    • Svenska
    • Tiếng Việt
    • Türkçe
    • Ελληνικά
    • Български език
    • Русский
    • Српски
    • Українська мова
    • עִבְרִית
    • العربية
    • فارسی
    • मराठी
    • हिन्दी
    • বাংলা
    • ગુજરાતી
    • தமிழ்
    • ಕನ್ನಡ
    • ภาษาไทย
    • 한국어
    • 日本語
    • 简体中文
    • 繁體中文
  • Have an account? Log in
    Have an account?
    · Forgot password?

    New to Twitter?
    Sign up
a13xp0p0v's profile
Alexander Popov
Alexander Popov
Alexander Popov
@a13xp0p0v

Tweets

Alexander Popov

@a13xp0p0v

Linux Kernel Developer & Security Researcher

Moscow
a13xp0p0v.github.io
Joined December 2012

Tweets

  • © 2020 Twitter
  • About
  • Help Center
  • Terms
  • Privacy policy
  • Imprint
  • Cookies
  • Ads info
Dismiss
Previous
Next

Go to a person's profile

Saved searches

  • Remove
  • In this conversation
    Verified accountProtected Tweets @
Suggested users
  • Verified accountProtected Tweets @
  • Verified accountProtected Tweets @

Promote this Tweet

Block

  • Tweet with a location

    You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more

    Your lists

    Create a new list


    Under 100 characters, optional

    Privacy

    Copy link to Tweet

    Embed this Tweet

    Embed this Video

    Add this Tweet to your website by copying the code below. Learn more

    Add this video to your website by copying the code below. Learn more

    Hmm, there was a problem reaching the server.

    By embedding Twitter content in your website or app, you are agreeing to the Twitter Developer Agreement and Developer Policy.

    Preview

    Why you're seeing this ad

    Log in to Twitter

    · Forgot password?
    Don't have an account? Sign up »

    Sign up for Twitter

    Not on Twitter? Sign up, tune into the things you care about, and get updates as they happen.

    Sign up
    Have an account? Log in »

    Two-way (sending and receiving) short codes:

    Country Code For customers of
    United States 40404 (any)
    Canada 21212 (any)
    United Kingdom 86444 Vodafone, Orange, 3, O2
    Brazil 40404 Nextel, TIM
    Haiti 40404 Digicel, Voila
    Ireland 51210 Vodafone, O2
    India 53000 Bharti Airtel, Videocon, Reliance
    Indonesia 89887 AXIS, 3, Telkomsel, Indosat, XL Axiata
    Italy 4880804 Wind
    3424486444 Vodafone
    » See SMS short codes for other countries

    Confirmation

     

    Welcome home!

    This timeline is where you’ll spend most of your time, getting instant updates about what matters to you.

    Tweets not working for you?

    Hover over the profile pic and click the Following button to unfollow any account.

    Say a lot with a little

    When you see a Tweet you love, tap the heart — it lets the person who wrote it know you shared the love.

    Spread the word

    The fastest way to share someone else’s Tweet with your followers is with a Retweet. Tap the icon to send it instantly.

    Join the conversation

    Add your thoughts about any Tweet with a Reply. Find a topic you’re passionate about, and jump right in.

    Learn the latest

    Get instant insight into what people are talking about now.

    Get more of what you love

    Follow more accounts to get instant updates about topics you care about.

    Find what's happening

    See the latest conversations about any topic instantly.

    Never miss a Moment

    Catch up instantly on the best stories happening as they unfold.

    Alexander Popov‏ @a13xp0p0v Jan 23
    • Report Tweet

    ========================= The Life and Incredible Adventures of One QEMU Bug (Which I Finally Fixed) ========================= A thread [1/n]

    3:11 AM - 23 Jan 2020
    • 40 Retweets
    • 118 Likes
    • libcamera swym Mani Sadhasivam StrikeBhack Tripoloski! Gustavo A. R. Silva Thomas C. Jamie Sparrow ALex Nikonov
    4 replies 40 retweets 118 likes
      1. New conversation
      2. Alexander Popov‏ @a13xp0p0v Jan 23
        • Report Tweet

        _Disclaimer_ That is not for trolling, that is for LOL. So here I omit the names of QEMU maintainers that were involved in these adventures. I will call them Mr1 and Mr2. Have fun! [2/n]

        1 reply 0 retweets 6 likes
        Show this thread
      3. Alexander Popov‏ @a13xp0p0v Jan 23
        • Report Tweet

        This bug was born in July 2015, in a lovely QEMU file called hw/ide/core.c. It was not very serious or critical like others. So you would not be very frustrated if you meet it on the way. I will not speak about its father. Let me keep the intrigue till the end. [3/n]

        1 reply 0 retweets 3 likes
        Show this thread
      4. Alexander Popov‏ @a13xp0p0v Jan 23
        • Report Tweet

        This bug couldn't read or write (what a pity!). It only asserted that the size of successful DMA transfers handled in ide_dma_cb() should be multiple of 512 (the size of a sector). ... 4 years later... [4/n]

        1 reply 0 retweets 2 likes
        Show this thread
      5. Alexander Popov‏ @a13xp0p0v Jan 23
        • Report Tweet

        One misty morning I logged into my fuzzing machine wondering why syzkaller hadn't given any useful results for several weeks. I've found QEMU crashed. Wow, syzkaller learned how to destroy its own environment :-/ [5/n]

        2 replies 0 retweets 7 likes
        Show this thread
      6. Alexander Popov‏ @a13xp0p0v Jan 23
        • Report Tweet

        It looked like QEMU guest-to-host DoS, so I prepared the fixing patch and decided to send it to QEMU security team. Yes, I'm doing responsible disclosure, folks :-) Then the crawling fun began. [6/n]

        2 replies 0 retweets 3 likes
        Show this thread
      7. Alexander Popov‏ @a13xp0p0v Jan 23
        • Report Tweet

        [Jun 20] me: sent PoC and patch to QEMU security team [Jun 26] me: hey, friendly ping! [Jul 05] secteam: Please feel free to send the patch upstream me: no problem, sent PoC and patch to the public ML https://lists.nongnu.org/archive/html/qemu-devel/2019-07/msg01651.html … [7/n]

        2 replies 0 retweets 1 like
        Show this thread
      8. Alexander Popov‏ @a13xp0p0v Jan 23
        • Report Tweet

        [Jul 15] me: public friendly ping [Jul 16] Mr1: hey Mr2, it's for you! Mr2: I'm aware of the patch. It's on the list to investigate today. /* 10 days passed... Huh? */ [8/n]

        1 reply 0 retweets 1 like
        Show this thread
      9. Alexander Popov‏ @a13xp0p0v Jan 23
        • Report Tweet

        [Jul 26] Mr2: oh, this is fun. Not gonna take your fix. Whole code should be overwritten. I can worry about a proper fix for QEMU 4.2+. [Jul 27] me: hum, okay... Feel free to add me to CC, I can review the patches and test them with fuzzing! /* 3.5 months passed... */ [9/n]

        1 reply 0 retweets 1 like
        Show this thread
      10. Alexander Popov‏ @a13xp0p0v Jan 23
        • Report Tweet

        Alexander Popov Retweeted Alexander Popov

        [Nov 6] me: I'm pointing politely to this issue again. It crashes qemu during syzkaller fuzzing. Why don't you apply my commit and then do the refactoring later when you want? [Nov 7] somebody in ML: do you want to rework the code yourself? https://twitter.com/a13xp0p0v/status/1192030766471032833 … [10/n]

        Alexander Popov added,

        Alexander Popov @a13xp0p0v
        Pinging QEMU maintainers patiently after 4 months of waiting: https://lists.nongnu.org/archive/html/qemu-devel/2019-11/msg00597.html … Why don't they apply my commit and then do the global refactoring later when they want? https://twitter.com/a13xp0p0v/status/1147181324178010112 …
        1 reply 0 retweets 1 like
        Show this thread
      11. Alexander Popov‏ @a13xp0p0v Jan 23
        • Report Tweet

        [Nov 7] me: huh, yes, I will take this task and return with a patch. /* Grr. Challenge accepted! A week of development. */ [Nov 14] me: new patch fixing IDE [Nov 21] Mr1: we have unit tests. First you improve them to cover all cases. Do according the IDE specification. [11/n]

        1 reply 0 retweets 2 likes
        Show this thread
      12. Alexander Popov‏ @a13xp0p0v Jan 23
        • Report Tweet

        [Nov 27] me: okay, it looks like I can do that https://lists.nongnu.org/archive/html/qemu-devel/2019-11/msg04403.html … /* More work done. I developed a new IDE fix and a shiny unit-test that also found an extra DMA emulation bug */ [Dec 16] me: sent the patch series [12/n]

        1 reply 0 retweets 2 likes
        Show this thread
      13. Alexander Popov‏ @a13xp0p0v Jan 23
        • Report Tweet

        [Dec 19] Mr1: No, your unit-test is slow. Make it faster. me: okay, I'll do that... https://lists.nongnu.org/archive/html/qemu-devel/2019-12/msg04442.html … /* More work done. Rrrrr! It must be finished! */ [13/n]

        1 reply 0 retweets 3 likes
        Show this thread
      14. Alexander Popov‏ @a13xp0p0v Jan 23
        • Report Tweet

        [Dec 23] me: new fast shiny unit-test and fix https://lists.nongnu.org/archive/html/qemu-devel/2019-12/msg05135.html … [Dec 24] Mr2: I've been out to lunch for a little while. I'll review these series before the end of the year. [Dec 28] me: hello anybody? /* Silence. Happy New Year! No review. LOL!!! */ [14/n]

        1 reply 0 retweets 2 likes
        Show this thread
      15. Alexander Popov‏ @a13xp0p0v Jan 23
        • Report Tweet

        Meanwhile my friends at 36C3 recommended to request a CVE to speed up the review process :-) Nice idea! Red Had likes CVEs! So MITRE allocated CVE-2019-20175 for this issue (with a DISPUTED tag). https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-20175 … [15/n]

        1 reply 0 retweets 5 likes
        Show this thread
      16. Alexander Popov‏ @a13xp0p0v Jan 23
        • Report Tweet

        [Jan 2] me: Happy New Year everyone! There is a CVE. How about review? /* 5 days passed */ [Jan 7] Mr1: okay, it's fine now. [Jan 8] me: thank you a lot! Let's wait for more reviews. /* 2 weeks passed */ [16/n]

        1 reply 0 retweets 2 likes
        Show this thread
      17. Alexander Popov‏ @a13xp0p0v Jan 23
        • Report Tweet

        [Jan 22] me: pinging in the ML again about this fix and unit-test! [Jan 22] Mr1: I asked Mr2. He promised to take a look very soon! [Jan 23] Mr2: merged. https://github.com/jnsnow/qemu/commits/ide … WOW! Really?!! [17/n]

        1 reply 0 retweets 2 likes
        Show this thread
      18. Alexander Popov‏ @a13xp0p0v Jan 23
        • Report Tweet

        And now can you guess who created this bug back in 2015? Yes, it was Mr2. LOL! Maybe that is why he was delaying the fix that killed it. That was weird story. Hope you liked it. Happy end! ========================= [n/n]pic.twitter.com/cqqSUDX9aX

        4 replies 1 retweet 15 likes
        Show this thread
      19. Alexander Popov‏ @a13xp0p0v Jan 23
        • Report Tweet

        And let me thank Mr1 once again! He is cool! I would not be able to become a QEMU contributor without his help :-) [n+1/n]

        2 replies 0 retweets 12 likes
        Show this thread
      20. End of conversation

    Loading seems to be taking a while.

    Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

      Promoted Tweet

      false

      • © 2020 Twitter
      • About
      • Help Center
      • Terms
      • Privacy policy
      • Imprint
      • Cookies
      • Ads info