{"push_id":2537583179,"size":192,"distinct_size":192,"ref":"refs/heads/4.14-lts","head":"906aefbc1d8ab1c5c1b0331ec29af5d10b40c9b7","before":"030a3505038d9bebff7a0d0d5ef9fff8b572e096","commits":[{"sha":"1a538cb0879d8646437836d540b6e952d9103f63","author":{"name":"Eric Biggers","email":"6f6115196800bbe9712b3f04c7e40093bb382fc5@google.com"},"message":"ext4: prevent right-shifting extents beyond EXT_MAX_BLOCKS\n\ncommit 349fa7d6e1935f49bf4161c4900711b2989180a9 upstream.\n\nDuring the \"insert range\" fallocate operation, extents starting at the\nrange offset are shifted \"right\" (to a higher file offset) by the range\nlength.  But, as shown by syzbot, it's not validated that this doesn't\ncause extents to be shifted beyond EXT_MAX_BLOCKS.  In that case\n->ee_block can wrap around, corrupting the extent tree.\n\nFix it by returning an error if the space between the end of the last\nextent and EXT4_MAX_BLOCKS is smaller than the range being inserted.\n\nThis bug can be reproduced by running the following commands when the\ncurrent directory is on an ext4 filesystem with a 4k block size:\n\n        fallocate -l 8192 file\n        fallocate --keep-size -o 0xfffffffe000 -l 4096 -n file\n        fallocate --insert-range -l 8192 file\n\nThen after unmounting the filesystem, e2fsck reports corruption.\n\nReported-by: syzbot+06c885be0edcdaeab40c@syzkaller.appspotmail.com\nFixes: 331573febb6a (\"ext4: Add support FALLOC_FL_INSERT_RANGE for fallocate\")\nCc: stable@vger.kernel.org # v4.2+\nSigned-off-by: Eric Biggers <ebiggers@google.com>\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/anthraxx/linux-hardened/commits/1a538cb0879d8646437836d540b6e952d9103f63"},{"sha":"4a3674acbf8b076bb42b68f5d95f0877acabf210","author":{"name":"Theodore Ts'o","email":"4ed386e0495d3e109932df055831d9ec2f824927@mit.edu"},"message":"ext4: set h_journal if there is a failure starting a reserved handle\n\ncommit b2569260d55228b617bd82aba6d0db2faeeb4116 upstream.\n\nIf ext4 tries to start a reserved handle via\njbd2_journal_start_reserved(), and the journal has been aborted, this\ncan result in a NULL pointer dereference.  This is because the fields\nh_journal and h_transaction in the handle structure share the same\nmemory, via a union, so jbd2_journal_start_reserved() will clear\nh_journal before calling start_this_handle().  If this function fails\ndue to an aborted handle, h_journal will still be NULL, and the call\nto jbd2_journal_free_reserved() will pass a NULL journal to\nsub_reserve_credits().\n\nThis can be reproduced by running \"kvm-xfstests -c dioread_nolock\ngeneric/475\".\n\nCc: stable@kernel.org # 3.11\nFixes: 8f7d89f36829b (\"jbd2: transaction reservation support\")\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nReviewed-by: Andreas Dilger <adilger@dilger.ca>\nReviewed-by: Jan Kara <jack@suse.cz>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/anthraxx/linux-hardened/commits/4a3674acbf8b076bb42b68f5d95f0877acabf210"},{"sha":"55cc3bb0a6c7da92dd1332cc8e1651dc2be89bfc","author":{"name":"Theodore Ts'o","email":"4ed386e0495d3e109932df055831d9ec2f824927@mit.edu"},"message":"ext4: add MODULE_SOFTDEP to ensure crc32c is included in the initramfs\n\ncommit 7ef79ad52136712172eb0525bf0b462516bf2f93 upstream.\n\nFixes: a45403b51582 (\"ext4: always initialize the crc32c checksum driver\")\nReported-by: François Valenduc <francoisvalenduc@gmail.com>\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nCc: stable@vger.kernel.org\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/anthraxx/linux-hardened/commits/55cc3bb0a6c7da92dd1332cc8e1651dc2be89bfc"},{"sha":"b39430ea068797bb45b72429db3743064280b1be","author":{"name":"Theodore Ts'o","email":"4ed386e0495d3e109932df055831d9ec2f824927@mit.edu"},"message":"ext4: add validity checks for bitmap block numbers\n\ncommit 7dac4a1726a9c64a517d595c40e95e2d0d135f6f upstream.\n\nAn privileged attacker can cause a crash by mounting a crafted ext4\nimage which triggers a out-of-bounds read in the function\next4_valid_block_bitmap() in fs/ext4/balloc.c.\n\nThis issue has been assigned CVE-2018-1093.\n\nBugLink: https://bugzilla.kernel.org/show_bug.cgi?id=199181\nBugLink: https://bugzilla.redhat.com/show_bug.cgi?id=1560782\nReported-by: Wen Xu <wen.xu@gatech.edu>\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nCc: stable@vger.kernel.org\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/anthraxx/linux-hardened/commits/b39430ea068797bb45b72429db3743064280b1be"},{"sha":"ae0db58dabe5463dcbcce095e83177536ed22d6a","author":{"name":"Lukas Czerner","email":"6c9141d0e2318b390a8a6bf8ecd9f819d16f05b4@redhat.com"},"message":"ext4: fix bitmap position validation\n\ncommit 22be37acce25d66ecf6403fc8f44df9c5ded2372 upstream.\n\nCurrently in ext4_valid_block_bitmap() we expect the bitmap to be\npositioned anywhere between 0 and s_blocksize clusters, but that's\nwrong because the bitmap can be placed anywhere in the block group. This\ncauses false positives when validating bitmaps on perfectly valid file\nsystem layouts. Fix it by checking whether the bitmap is within the group\nboundary.\n\nThe problem can be reproduced using the following\n\nmkfs -t ext3 -E stride=256 /dev/vdb1\nmount /dev/vdb1 /mnt/test\ncd /mnt/test\nwget https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-4.16.3.tar.xz\ntar xf linux-4.16.3.tar.xz\n\nThis will result in the warnings in the logs\n\nEXT4-fs error (device vdb1): ext4_validate_block_bitmap:399: comm tar: bg 84: block 2774529: invalid block bitmap\n\n[ Changed slightly for clarity and to not drop a overflow test -- TYT ]\n\nSigned-off-by: Lukas Czerner <lczerner@redhat.com>\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nReported-by: Ilya Dryomov <idryomov@gmail.com>\nFixes: 7dac4a1726a9 (\"ext4: add validity checks for bitmap block numbers\")\nCc: stable@vger.kernel.org\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/anthraxx/linux-hardened/commits/ae0db58dabe5463dcbcce095e83177536ed22d6a"},{"sha":"812b51a630005ed8d0a947bece1f430474b724bf","author":{"name":"Theodore Ts'o","email":"4ed386e0495d3e109932df055831d9ec2f824927@mit.edu"},"message":"random: set up the NUMA crng instances after the CRNG is fully initialized\n\ncommit 8ef35c866f8862df074a49a93b0309725812dea8 upstream.\n\nUntil the primary_crng is fully initialized, don't initialize the NUMA\ncrng nodes.  Otherwise users of /dev/urandom on NUMA systems before\nthe CRNG is fully initialized can get very bad quality randomness.  Of\ncourse everyone should move to getrandom(2) where this won't be an\nissue, but there's a lot of legacy code out there.  This related to\nCVE-2018-1108.\n\nReported-by: Jann Horn <jannh@google.com>\nFixes: 1e7f583af67b (\"random: make /dev/urandom scalable for silly...\")\nCc: stable@kernel.org # 4.8+\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/anthraxx/linux-hardened/commits/812b51a630005ed8d0a947bece1f430474b724bf"},{"sha":"ffc5b50a2b53d180d977b969034cad1a9fb45d8b","author":{"name":"Theodore Ts'o","email":"4ed386e0495d3e109932df055831d9ec2f824927@mit.edu"},"message":"random: fix possible sleeping allocation from irq context\n\ncommit 6c1e851c4edc13a43adb3ea4044e3fc8f43ccf7d upstream.\n\nWe can do a sleeping allocation from an irq context when CONFIG_NUMA\nis enabled.  Fix this by initializing the NUMA crng instances in a\nworkqueue.\n\nReported-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>\nReported-by: syzbot+9de458f6a5e713ee8c1a@syzkaller.appspotmail.com\nFixes: 8ef35c866f8862df (\"random: set up the NUMA crng instances...\")\nCc: stable@vger.kernel.org\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/anthraxx/linux-hardened/commits/ffc5b50a2b53d180d977b969034cad1a9fb45d8b"},{"sha":"76dbabb38a18ff7ec20de36e9dabcadccca9ad69","author":{"name":"Theodore Ts'o","email":"4ed386e0495d3e109932df055831d9ec2f824927@mit.edu"},"message":"random: rate limit unseeded randomness warnings\n\ncommit 4e00b339e264802851aff8e73cde7d24b57b18ce upstream.\n\nOn systems without sufficient boot randomness, no point spamming dmesg.\n\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nCc: stable@vger.kernel.org\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/anthraxx/linux-hardened/commits/76dbabb38a18ff7ec20de36e9dabcadccca9ad69"},{"sha":"470bf16ae1ab7172133fe3c6b4506a75f86d314f","author":{"name":"Shuah Khan","email":"c62751f8c6ce7eb0639cab80a821801931863a4b@osg.samsung.com"},"message":"usbip: usbip_event: fix to not print kernel pointer address\n\ncommit 4c982482341c64f55daf69b6caa5a2bcd9b43824 upstream.\n\nFix it to not print kernel pointer address. Remove the conditional\nand debug message as it isn't very useful.\n\nSigned-off-by: Shuah Khan <shuahkh@osg.samsung.com>\nCc: stable <stable@vger.kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/anthraxx/linux-hardened/commits/470bf16ae1ab7172133fe3c6b4506a75f86d314f"},{"sha":"944edaf13deeb0db5847bddf956c4316e53d6f2c","author":{"name":"Shuah Khan","email":"c62751f8c6ce7eb0639cab80a821801931863a4b@osg.samsung.com"},"message":"usbip: usbip_host: fix to hold parent lock for device_attach() calls\n\ncommit 4bfb141bc01312a817d36627cc47c93f801c216d upstream.\n\nusbip_host calls device_attach() without holding dev->parent lock.\nFix it.\n\nSigned-off-by: Shuah Khan <shuahkh@osg.samsung.com>\nCc: stable <stable@vger.kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/anthraxx/linux-hardened/commits/944edaf13deeb0db5847bddf956c4316e53d6f2c"},{"sha":"4abe5b775a16e131466f40861b90632d719da1b5","author":{"name":"Shuah Khan","email":"c62751f8c6ce7eb0639cab80a821801931863a4b@osg.samsung.com"},"message":"usbip: vhci_hcd: Fix usb device and sockfd leaks\n\ncommit 9020a7efe537856eb3e826ebebdf38a5d07a7857 upstream.\n\nvhci_hcd fails to do reset to put usb device and sockfd in the\nmodule remove/stop paths. Fix the leak.\n\nSigned-off-by: Shuah Khan <shuahkh@osg.samsung.com>\nCc: stable <stable@vger.kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/anthraxx/linux-hardened/commits/4abe5b775a16e131466f40861b90632d719da1b5"},{"sha":"b792b1f7d01ca95db8b39046e2a539def5ffc4f2","author":{"name":"Shuah Khan","email":"c62751f8c6ce7eb0639cab80a821801931863a4b@osg.samsung.com"},"message":"usbip: vhci_hcd: check rhport before using in vhci_hub_control()\n\ncommit 5b22f676118ff25049382041da0db8012e57c9e8 upstream.\n\nValidate !rhport < 0 before using it to access port_status array.\n\nSigned-off-by: Shuah Khan <shuahkh@osg.samsung.com>\nCc: stable <stable@vger.kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/anthraxx/linux-hardened/commits/b792b1f7d01ca95db8b39046e2a539def5ffc4f2"},{"sha":"64abd2428e54ead122a4e713a0abfb9627fa3e02","author":{"name":"Greg Kroah-Hartman","email":"4645f7897fd33786a2ee1264d590b3c400559d85@linuxfoundation.org"},"message":"Revert \"xhci: plat: Register shutdown for xhci_plat\"\n\ncommit c20f53c58261b121d0989e147368803b9773b413 upstream.\n\nThis reverts commit b07c12517f2aed0add8ce18146bb426b14099392\n\nIt is incomplete and causes hangs on devices when shutting down.  It\nneeds a much more \"complete\" fix in order to work properly.  As that fix\nhas not been merged, revert this patch for now before it causes any more\nproblems.\n\nCc: Greg Hackmann <ghackmann@google.com>\nCc: Adam Wallis <awallis@codeaurora.org>\nCc: Mathias Nyman <mathias.nyman@intel.com>\nCc: stable <stable@vger.kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/anthraxx/linux-hardened/commits/64abd2428e54ead122a4e713a0abfb9627fa3e02"},{"sha":"0b932b1ca9dad9ba18b58efb56074d3431c81166","author":{"name":"Kai-Heng Feng","email":"06af28c154da900e58fef391e9e9415561e1d8ae@canonical.com"},"message":"xhci: Fix USB ports for Dell Inspiron 5775\n\ncommit 621faf4f6a181b6e012c1d1865213f36f4159b7f upstream.\n\nThe Dell Inspiron 5775 is a Raven Ridge. The Enable Slot command timed\nout when a USB device gets plugged:\n[ 212.156326] xhci_hcd 0000:03:00.3: Error while assigning device slot ID\n[ 212.156340] xhci_hcd 0000:03:00.3: Max number of devices this xHCI host supports is 64.\n[ 212.156348] usb usb2-port3: couldn't allocate usb_device\n\nAMD suggests that a delay before xHC suspends can fix the issue.\n\nI can confirm it fixes the issue, so use the suspend delay quirk for\nRaven Ridge's xHC.\n\nCc: stable@vger.kernel.org\nSigned-off-by: Kai-Heng Feng <kai.heng.feng@canonical.com>\nSigned-off-by: Mathias Nyman <mathias.nyman@linux.intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/anthraxx/linux-hardened/commits/0b932b1ca9dad9ba18b58efb56074d3431c81166"},{"sha":"8f30aa32b716b728163893a90be929f5e9e6c071","author":{"name":"Collin May","email":"016e57c89e3285b6cfaea483202c72c7a834aab4@collinswebsite.com"},"message":"USB: serial: simple: add libtransistor console\n\ncommit fe710508b6ba9d28730f3021fed70e7043433b2e upstream.\n\nAdd simple driver for libtransistor USB console.\nThis device is implemented in software:\nhttps://github.com/reswitched/libtransistor/blob/development/lib/usb_serial.c\n\nSigned-off-by: Collin May <collin@collinswebsite.com>\nCc: stable <stable@vger.kernel.org>\nSigned-off-by: Johan Hovold <johan@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/anthraxx/linux-hardened/commits/8f30aa32b716b728163893a90be929f5e9e6c071"},{"sha":"747120e77100fccc05923a104bca3e9c729af87b","author":{"name":"Vasyl Vavrychuk","email":"6b6ff1aeeddbf0f5c49ad097ffaf33464ac3d2e9@gmail.com"},"message":"USB: serial: ftdi_sio: use jtag quirk for Arrow USB Blaster\n\ncommit 470b5d6f0cf4674be2d1ec94e54283a1770b6a1a upstream.\n\nArrow USB Blaster integrated on MAX1000 board uses the same vendor ID\n(0x0403) and product ID (0x6010) as the \"original\" FTDI device.\n\nThis patch avoids picking up by ftdi_sio of the first interface of this\nUSB device. After that this device can be used by Arrow user-space JTAG\ndriver.\n\nSigned-off-by: Vasyl Vavrychuk <vvavrychuk@gmail.com>\nCc: stable <stable@vger.kernel.org>\nSigned-off-by: Johan Hovold <johan@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/anthraxx/linux-hardened/commits/747120e77100fccc05923a104bca3e9c729af87b"},{"sha":"f310eb70657e991c68c085e41b66e7c119cb392b","author":{"name":"Kyle Roeschley","email":"ca3201b7961668836d79bcab60556c323784a58a@ni.com"},"message":"USB: serial: cp210x: add ID for NI USB serial console\n\ncommit 1e23aace21515a8f7615a1de016c0ea8d4e0cc6e upstream.\n\nAdded the USB VID and PID for the USB serial console on some National\nInstruments devices.\n\nSigned-off-by: Kyle Roeschley <kyle.roeschley@ni.com>\nCc: stable <stable@vger.kernel.org>\nSigned-off-by: Johan Hovold <johan@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/anthraxx/linux-hardened/commits/f310eb70657e991c68c085e41b66e7c119cb392b"},{"sha":"333909311d70b035306a86b0139daaf480a25624","author":{"name":"Heikki Krogerus","email":"0364a60538b3766c953bdea7e7e4859afd98436c@linux.intel.com"},"message":"usb: typec: ucsi: Increase command completion timeout value\n\ncommit b1b59e16075f5e5da2943ce8de724ab96bc3c6c2 upstream.\n\nOn some boards, under heavy load, the EC firmware is\nunable to complete commands even in one second. Increasing\nthe command completion timeout value to five seconds.\n\nReported-by: Quanxian Wang <quanxian.wang@intel.com>\nFixes: c1b0bc2dabfa (\"usb: typec: Add support for UCSI interface\")\nCc: <stable@vger.kernel.org>\nSigned-off-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/anthraxx/linux-hardened/commits/333909311d70b035306a86b0139daaf480a25624"},{"sha":"c59dc4d135192123523f35ff60243295a4f9d40a","author":{"name":"Kamil Lulko","email":"5764a707aac3f90197a15da763f29d49e2436636@intel.com"},"message":"usb: core: Add quirk for HP v222w 16GB Mini\n\ncommit 3180dabe08e3653bf0a838553905d88f3773f29c upstream.\n\nAdd DELAY_INIT quirk to fix the following problem with HP\nv222w 16GB Mini:\n\nusb 1-3: unable to read config index 0 descriptor/start: -110\nusb 1-3: can't read configurations, error -110\nusb 1-3: can't set config #1, error -110\n\nSigned-off-by: Kamil Lulko <kamilx.lulko@intel.com>\nSigned-off-by: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com>\nCc: stable <stable@vger.kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/anthraxx/linux-hardened/commits/c59dc4d135192123523f35ff60243295a4f9d40a"},{"sha":"e6d2055ba32f0878b09f3068af10a4ba445f84a8","author":{"name":"Ravi Chandra Sadineni","email":"068c0dca42d898d893968d7098b20075cb89039f@chromium.org"},"message":"USB: Increment wakeup count on remote wakeup.\n\ncommit 83a62c51ba7b3c0bf45150c4eac7aefc6c785e94 upstream.\n\nOn chromebooks we depend on wakeup count to identify the wakeup source.\nBut currently USB devices do not increment the wakeup count when they\ntrigger the remote wake. This patch addresses the same.\n\nResume condition is reported differently on USB 2.0 and USB 3.0 devices.\n\nOn USB 2.0 devices, a wake capable device, if wake enabled, drives\nresume signal to indicate a remote wake (USB 2.0 spec section 7.1.7.7).\nThe upstream facing port then sets C_PORT_SUSPEND bit and reports a\nport change event (USB 2.0 spec section 11.24.2.7.2.3). Thus if a port\nhas resumed before driving the resume signal from the host and\nC_PORT_SUSPEND is set, then the device attached to the given port might\nbe the reason for the last system wakeup. Increment the wakeup count for\nthe same.\n\nOn USB 3.0 devices, a function may signal that it wants to exit from device\nsuspend by sending a Function Wake Device Notification to the host (USB3.0\nspec section 8.5.6.4) Thus on receiving the Function Wake, increment the\nwakeup count.\n\nSigned-off-by: Ravi Chandra Sadineni <ravisadineni@chromium.org>\nAcked-by: Alan Stern <stern@rowland.harvard.edu>\nCc: stable <stable@vger.kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/anthraxx/linux-hardened/commits/e6d2055ba32f0878b09f3068af10a4ba445f84a8"}]}
{"actor":{"display_login":"anthraxx"}}