{"id":14963,"date":"2026-10-12T14:24:41","date_gmt":"2026-10-12T11:24:41","guid":{"rendered":"https:\/\/www.kaspersky.com.tr\/blog\/?p=14963"},"modified":"2026-10-12T14:24:41","modified_gmt":"2026-10-12T11:24:41","slug":"google-pixel-september-2026-security-update","status":"publish","type":"post","link":"https:\/\/www.kaspersky.com.tr\/blog\/google-pixel-september-2026-security-update\/14963\/","title":{"rendered":"Google, Pixel ak\u0131ll\u0131 telefonlardaki 110 zay\u0131f noktay\u0131 giderdi"},"content":{"rendered":"

15 Eyl\u00fcl\u2019de Google, kendi Google Pixel ak\u0131ll\u0131 telefonlar\u0131ndaki 110 zay\u0131f noktaya y\u00f6nelik yamalar\u0131n ayr\u0131nt\u0131lar\u0131n\u0131 yay\u0131nlad\u0131. A\u00e7\u0131klanan t\u00fcm g\u00fcvenlik a\u00e7\u0131klar\u0131 aras\u0131nda CVE-2026-58704<\/a> en \u00e7ok dikkat \u00e7ekeni; zira bu s\u0131f\u0131r g\u00fcn g\u00fcvenlik a\u00e7\u0131\u011f\u0131n\u0131n hedefli sald\u0131r\u0131larda istismar edildi\u011fi g\u00f6r\u00fcl\u00fcyor.<\/p>\n

Bug\u00fcnk\u00fc yaz\u0131m\u0131zda, Google Pixel\u2019de neyin bu kadar \u00f6zel oldu\u011funu ve bu cihazlar\u0131n neden normal Android g\u00fcncellemelerinden ayr\u0131 olarak kendilerine \u00f6zg\u00fc g\u00fcvenlik g\u00fcncellemeleri ald\u0131\u011f\u0131n\u0131 ele al\u0131yoruz. Ayr\u0131ca, bu son g\u00fcncellemede giderilen zay\u0131f noktalar\u0131 da inceliyoruz, \u00f6zellikle de bahsedilen en tehlikeli g\u00fcvenlik a\u00e7\u0131\u011f\u0131 olan CVE-2026-58704\u2019e odaklan\u0131yoruz ve yaz\u0131m\u0131z\u0131, cihaz\u0131n\u0131z\u0131 nas\u0131l koruyabilece\u011finiz ve cihaz\u0131n\u0131z \u00fczerinden siber sald\u0131r\u0131n\u0131n kurban\u0131 olmaktan nas\u0131l ka\u00e7\u0131nabilece\u011finiz konusunda ipu\u00e7lar\u0131yla sonland\u0131r\u0131yoruz.<\/p>\n

Google Pixel telefonlar\u0131 neden Android\u2019den ayr\u0131 olarak g\u00fcvenlik g\u00fcncellemeleri al\u0131yor?<\/h2>\n

Okuyucu hakl\u0131 olarak \u015f\u00f6yle d\u00fc\u015f\u00fcnebilir: Bu ay\u0131n Android g\u00fcvenlik g\u00fcncellemelerini Google Pixel cihaz\u0131ma zaten y\u00fckledim. Bu ayn\u0131 \u015fey de\u011fil mi? Google Pixel, Android \u00fczerinde \u00e7al\u0131\u015f\u0131r ve ayl\u0131k Android G\u00fcvenlik B\u00fclteninde<\/a> ayr\u0131nt\u0131lar\u0131 verilen bu g\u00fcvenlik g\u00fcncellemelerini al\u0131r. Ancak, Android tabanl\u0131 cihazlar\u0131n \u00fcreticileri farkl\u0131 donan\u0131m ve yaz\u0131l\u0131m bile\u015fenleri kullanmaktad\u0131r. Bu nedenle, t\u00fcm Android cihazlar\u0131nda ortak olarak g\u00f6r\u00fclen zay\u0131f noktalar\u0131n yan\u0131 s\u0131ra, her bir \u00fcreticinin cihazlar\u0131na \u00f6zg\u00fc g\u00fcvenlik sorunlar\u0131 da bulunur.<\/p>\n

Google, kendi ak\u0131ll\u0131 telefonlar\u0131 i\u00e7in ayr\u0131 g\u00fcvenlik g\u00fcncellemeleri yay\u0131nlamakta ve bu g\u00fcncellemeler, \u00f6zel bir Pixel G\u00fcncelleme B\u00fclteni<\/a> kapsam\u0131nda yer almaktad\u0131r. Bu belge, Android G\u00fcvenlik B\u00fclteninin yerini almak yerine, Google taraf\u0131ndan \u00fcretilen cihazlara \u00f6zg\u00fc zay\u0131f noktalar\u0131 ayr\u0131nt\u0131l\u0131 olarak a\u00e7\u0131klayarak onu zenginle\u015ftirmektedir. Di\u011fer Android ak\u0131ll\u0131 telefonlar da \u00fcreticileri taraf\u0131ndan benzer g\u00fcncellemeler al\u0131r.<\/p>\n

Eyl\u00fcl 2026 tarihli Pixel G\u00fcncelleme B\u00fclteni<\/a>, Google\u2019\u0131n ak\u0131ll\u0131 telefonlar\u0131 i\u00e7in neden ayr\u0131 g\u00fcncellemelere ihtiya\u00e7 duydu\u011funu a\u00e7\u0131k\u00e7a ortaya koyuyor. D\u00fczeltilen zay\u0131f noktalar\u0131n \u00e7o\u011fu; modem, \u00f6ny\u00fckleyici, GPU, parmak izi taray\u0131c\u0131 bile\u015fenleri ve cihaz\u0131n di\u011fer par\u00e7alar\u0131 gibi belirli Pixel donan\u0131m bile\u015fenlerini (veya donan\u0131mla ilgili bile\u015fenleri) etkiliyor. Di\u011fer \u00fcreticilerin ak\u0131ll\u0131 telefonlar\u0131nda bu \u00f6zellikler tamamen farkl\u0131 donan\u0131m ve yaz\u0131l\u0131m bile\u015fenlerine dayan\u0131yor olabilir; bu nedenle, Pixel G\u00fcncelleme B\u00fclteninde listelenen d\u00fczeltmeler bu telefonlar i\u00e7in ge\u00e7erli de\u011fildir.<\/p>\n

Bununla birlikte, bu zay\u0131f noktalar, cihazlar\u0131na \u00f6zel ROM y\u00fcklemi\u015f olan Pixel sahipleri i\u00e7in h\u00e2l\u00e2 ge\u00e7erli olabilir. Farkl\u0131 bir i\u015fletim sistemine ge\u00e7mek, cihaz\u0131n donan\u0131m bile\u015fenlerini de\u011fi\u015ftirmez ve ayg\u0131t yaz\u0131l\u0131m\u0131n\u0131 yenilemeyebilir. Bu nedenle, zay\u0131f noktalar varl\u0131\u011f\u0131n\u0131 s\u00fcrd\u00fcrebilir; ancak yamalar\u0131n mevcut olup olmad\u0131\u011f\u0131 ve bunlar\u0131n nas\u0131l kurulaca\u011f\u0131, kullan\u0131lan i\u015fletim sistemine g\u00f6re de\u011fi\u015fir.<\/p>\n

CVE-2026-58704: Yayg\u0131n olarak aktif bir \u015fekilde istismar edilen bir s\u0131f\u0131r g\u00fcn zay\u0131f noktas\u0131<\/h2>\n

\u015eimdi, Google\u2019\u0131n Eyl\u00fcl ay\u0131nda giderdi\u011fi belirli zay\u0131f noktalara daha yak\u0131ndan bakal\u0131m. Bunlardan en \u00f6nemlisi, yukar\u0131da belirtilen CVE-2026-58704\u2019t\u00fcr<\/a>.<\/p>\n

Bu zay\u0131f nokta, ak\u0131ll\u0131 telefonun h\u00fccresel a\u011flarla ileti\u015fimini sa\u011flayan H\u00fccresel Modem bile\u015fenini etkiler. Bu durum, koddaki bir mant\u0131k hatas\u0131ndan kaynaklan\u0131r; bu hata, belirli ko\u015fullar alt\u0131nda, ama\u00e7lanan izin kontrol\u00fcn\u00fcn atlanmas\u0131na olanak tan\u0131r.<\/p>\n

CVE-2026-58704 g\u00fcvenlik a\u00e7\u0131\u011f\u0131n\u0131n ba\u015far\u0131l\u0131 bir \u015fekilde istismar edilmesi, sald\u0131rganlar\u0131n ak\u0131ll\u0131 telefondaki ayr\u0131cal\u0131klar\u0131n\u0131 y\u00fckseltmelerine ve cihaz\u0131n i\u015flevlerine ve verilerine daha geni\u015f eri\u015fim elde etmelerine izin verir. Sald\u0131r\u0131n\u0131n bir mobil a\u011f \u00fczerinden ger\u00e7ekle\u015fti\u011fini ve sald\u0131rganlar\u0131n ba\u015flang\u0131\u00e7ta hedef cihazda d\u00fc\u015f\u00fck d\u00fczeyde eri\u015fim haklar\u0131na ihtiya\u00e7 duyduklar\u0131n\u0131 unutmay\u0131n.<\/p>\n

Uygulamada bu, sald\u0131rganlar\u0131n CVE-2026-58704 g\u00fcvenlik a\u00e7\u0131\u011f\u0131n\u0131 kullanarak internet \u00fczerinden herhangi bir yerden bir Pixel cihaz\u0131na sald\u0131r\u0131 d\u00fczenleyemeyecekleri anlam\u0131na gelir; \u00e7\u00fcnk\u00fc g\u00f6r\u00fcn\u00fc\u015fe g\u00f6re ya hedef ak\u0131ll\u0131 telefonun halihaz\u0131rda ba\u011fl\u0131 oldu\u011fu h\u00fccresel a\u011f\u0131 ele ge\u00e7irmeleri ya da, daha b\u00fcy\u00fck olas\u0131l\u0131kla, cihaz\u0131 kendi kontrol\u00fc alt\u0131ndaki k\u00f6t\u00fc ama\u00e7l\u0131 bir baz istasyonuna ba\u011flanmaya zorlamalar\u0131 gerekir.<\/p>\n

Google, bu g\u00fcvenlik a\u00e7\u0131\u011f\u0131n\u0131n t\u00fcm ayr\u0131nt\u0131lar\u0131n\u0131 hen\u00fcz a\u00e7\u0131klamad\u0131 ve ilgili rapora kamuoyu taraf\u0131ndan eri\u015filemiyor. Sonu\u00e7 olarak, sald\u0131rganlar\u0131n CVE-2026-58704 g\u00fcvenlik a\u00e7\u0131\u011f\u0131n\u0131 ne kadar kolay istismar edebilece\u011fini ortaya koyacak teknik ayr\u0131nt\u0131lar, t\u00fcm cihazlara yamalar\u0131n y\u00fcklenmesine kadar bilinmeyecektir.<\/p>\n

Bununla birlikte, Google, CVE-2026-58704\u2019\u00fcn s\u0131n\u0131rl\u0131 \u00f6l\u00e7\u00fcde istismar edildi\u011fine dair i\u015faretler oldu\u011funu iddia ediyor.<\/p>\n

Di\u011fer 109 zay\u0131f nokta hakk\u0131nda bildiklerimiz<\/h2>\n

Google Pixel cihazlar\u0131nda tespit edilen geri kalan 109 zay\u0131f noktan\u0131n sadece biri \u201corta\u201d d\u00fczeyde olarak de\u011ferlendirilmi\u015ftir; di\u011ferleri ise ya \u201cy\u00fcksek\u201d (62) ya da \u201ckritik\u201d (46) d\u00fczeyindedir. Bu g\u00fcvenlik a\u00e7\u0131klar\u0131ndan dokuzu, RCE (uzaktan kod y\u00fcr\u00fctme) kategorisine girmektedir. Bu, bir sald\u0131rgan\u0131n bu zay\u0131f noktalardan birini ba\u015far\u0131yla istismar etmesi durumunda, cihaz\u0131 uzaktan k\u00f6t\u00fc ama\u00e7l\u0131 kod \u00e7al\u0131\u015ft\u0131rmaya zorlayabilece\u011fi anlam\u0131na gelir. Sald\u0131r\u0131n\u0131n tam ko\u015fullar\u0131, s\u00f6z konusu zay\u0131f noktaya ba\u011fl\u0131d\u0131r.<\/p>\n

88 zay\u0131f nokta daha, ayr\u0131cal\u0131k y\u00fckseltme (EoP) kategorisine girer. Bu a\u00e7\u0131klar, cihaza halihaz\u0131rda belirli bir eri\u015fim d\u00fczeyine sahip olan bir sald\u0131rgan\u0131n yetkilerini geni\u015fletmesine olanak tan\u0131r. Yukar\u0131da ele al\u0131nan CVE-2026-58704 zay\u0131f nokta da bu kategoriye giriyor, bu nedenle Eyl\u00fcl ay\u0131 b\u00fclteninde toplam 89 adet EoP zay\u0131f noktas\u0131 listelenmi\u015ftir.<\/p>\n

Son olarak, 10 zay\u0131f nokta bilgi s\u0131zmas\u0131na (ID), iki zay\u0131f nokta ise hizmet reddi (DoS) durumuna yol a\u00e7abilir. K\u0131sacas\u0131, bu olduk\u00e7a uzun bir sorun listesi; bu nedenle Google Pixel kullan\u0131c\u0131lar\u0131 yamalar\u0131 y\u00fcklemek i\u00e7in \u00e7ok beklememeli.<\/p>\n

Ma\u011fdur olmaktan nas\u0131l ka\u00e7\u0131n\u0131l\u0131r?<\/h2>\n

Google Pixel kullan\u0131c\u0131lar\u0131, bu yaz\u0131da ele al\u0131nan zay\u0131f noktalar\u0131 gideren g\u00fcncellemeyi \u015fu yolu izleyerek y\u00fckleyebilirler: Ayarlar<\/em> \u2192 G\u00fcvenlik ve gizlilik<\/em> \u2192 Sistem ve g\u00fcncellemeler<\/em> \u2192 G\u00fcvenlik g\u00fcncellemesi<\/em> \u2192 Y\u00fckle<\/em>. G\u00fcncellemenin y\u00fcklenmesini tamamlamak i\u00e7in telefonun otomatik olarak yeniden ba\u015flat\u0131laca\u011f\u0131n\u0131 unutmay\u0131n.<\/p>\n

Telefonunuzun g\u00fcvenli\u011fini sa\u011flamak i\u00e7in a\u015fa\u011f\u0131daki genel \u00f6nlemleri alman\u0131z\u0131 \u00f6neririz:<\/p>\n